Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(ci): use same branching schema for e2e #28493

Merged

Conversation

mdelapenya
Copy link
Contributor

What does this PR do?

When triggering the e2e tests for Beats branches, we want to follow the same branch name schema than in Beats.

For that reason we are renaming e2e's maintenance branches from 7.15.x to 7.15

Why is it important?

Consistency across related projects, aligining with stack versions

@mdelapenya mdelapenya self-assigned this Oct 18, 2021
@mdelapenya mdelapenya added the Team:Automation Label for the Observability productivity team label Oct 18, 2021
@mdelapenya mdelapenya requested a review from a team October 18, 2021 09:21
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Oct 18, 2021
@mdelapenya
Copy link
Contributor Author

Do not merge until e2e-testing project renames its branches

@mdelapenya mdelapenya added backport-v7.14.0 Automated backport with mergify backport-v7.15.0 Automated backport with mergify labels Oct 18, 2021
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-10-18T09:21:43.812+0000

  • Duration: 15 min 58 sec

  • Commit: 8d0dca4

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

@mdelapenya mdelapenya changed the title chore: use same branching schema for e2e chore(ci): use same branching schema for e2e Oct 18, 2021
@mdelapenya mdelapenya marked this pull request as ready for review October 18, 2021 13:21
@mdelapenya mdelapenya merged commit 055e859 into elastic:7.x Oct 18, 2021
mergify bot pushed a commit that referenced this pull request Oct 18, 2021
mergify bot pushed a commit that referenced this pull request Oct 18, 2021
v1v added a commit that referenced this pull request Oct 18, 2021
* upstream/7.x:
  chore: use same branching schema for e2e (#28493)
  [Automation] Update elastic stack version to 7.16.0-8bf0b9b1 for testing (#28484)
  chore(ci): remove not used param when triggering e2e tests (#27823) (#27828)
  Add deprecation warning for filebeat disabled modules (#28393)
  Run Python tests in libbeat (#28438) (#28485)
  Register `storage_account` as second name for `storage` metricset  (#28447) (#28470)
  [CI] Add E2E for x-pack/elastic-agent (fleet) (#24112) (#28465)
@mdelapenya mdelapenya deleted the use-beats-branching-schema-in-e2e branch October 19, 2021 09:26
mdelapenya added a commit that referenced this pull request Oct 19, 2021
(cherry picked from commit 055e859)

Co-authored-by: Manuel de la Peña <[email protected]>
mdelapenya added a commit that referenced this pull request Oct 19, 2021
(cherry picked from commit 055e859)

Co-authored-by: Manuel de la Peña <[email protected]>
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
(cherry picked from commit e51835b)

Co-authored-by: Manuel de la Peña <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v7.14.0 Automated backport with mergify backport-v7.15.0 Automated backport with mergify Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants