automation: update next branch

[v1v]

What does this PR do?

Script to update the CI/Automation scripts from a given major.minor branch to another major.minor branch.

Why is it important?

This is the very first attempt to automate the branch creation when a new minor branch is created.

We need to figure out when this script should be triggered, in addition the branch creation should be done from the main branch ideally, but again, that's something to be discussed.

This PR is based on the changes done in #1938

[mergify]

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[elasticmachine]

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-01-11T11:11:36.964+0000

• Duration: 62 min 26 sec

• Commit: cd56b1b

Test stats 🧪

Test	Results
Failed	1
Passed	211
Skipped	0
Total	212

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / kubernetes_autodiscover_elastic-agent / [empty] – TEST-x86_64-kubernetes-autodiscover-ce1dae37-2022-01-11-11:31:01.xml

• no error details
Expand to view the stacktrace

 Test report file /var/lib/jenkins/workspace/PR-1991-1-bb5cb2f5-72c6-4d6a-91e5-6178975e2cce/outputs/3.133.108.222/TEST-x86_64-kubernetes-autodiscover-ce1dae37-2022-01-11-11:31:01.xml was length 0 

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Initializing / End-To-End Tests / kubernetes_autodiscover_elastic-agent / [empty] – TEST-x86_64-kubernetes-autodiscover-ce1dae37-2022-01-11-11:31:01.xml

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[mdelapenya]

Would this place a good one to bump the upgrade agent version?

[v1v]

What file did I miss?

[mdelapenya]

No, no... not suggesting there is a file missing. Just checking if this file would be, in a follow-up work, the one to add bumps for the upgrade-agent version, which hurts us when the last minor version (minor.version - 2) disappears from the artifactory

[kuisathaverat]

outdated