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

[JJBB][CI] Run beats-tester on master and release branches #21169

Merged
merged 6 commits into from
Sep 21, 2020

Conversation

v1v
Copy link
Member

@v1v v1v commented Sep 18, 2020

What does this PR do?

Create MBP for running beats-tester when the packaging has been successfully executed for the master and release branches.

NOTE: It does not support BCs but SNAPSHOTS

It also supports PullRequests, how?

  • Create packaging (with comment /packaging) then the beats-tester will be executed

Why is it important?

This will help to validate the installers for every commit that has been successfully validated in the CI.

Related issues

Closes elastic/beats-tester#176

@v1v v1v added automation ci Team:Automation Label for the Observability productivity team labels Sep 18, 2020
@v1v v1v requested a review from a team September 18, 2020 12:13
@v1v v1v self-assigned this Sep 18, 2020
@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 Sep 18, 2020
@elasticmachine
Copy link
Collaborator

elasticmachine commented Sep 18, 2020

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: [Pull request #21169 updated]

  • Start Time: 2020-09-18T12:32:15.774+0000

  • Duration: 23 min 0 sec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation ci Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Run beats-tester for release branches
3 participants