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

ci: enable build notifications as GitHub issues #1582

Merged
merged 2 commits into from
Jun 23, 2022

Conversation

v1v
Copy link
Member

@v1v v1v commented Jun 22, 2022

What does this PR do?

Create a GitHub issue:

  • As soon as a build is failing an issue should be created
  • It should be assigned to Elastic Agent Data Plane team (it relies on the GitHub labels to do so)

Why is it important?

Use GitHub to drive the on-call process when the CI fails

Related issues

Similar to elastic/beats#31954

@v1v v1v added automation backport-v8.3.0 Automated backport with mergify backport-7.17 Automated backport to the 7.17 branch with mergify labels Jun 22, 2022
@v1v v1v requested review from ph, jlind23 and a team June 22, 2022 16:13
@v1v v1v requested a review from a team as a code owner June 22, 2022 16:13
@v1v v1v self-assigned this Jun 22, 2022
.ci/Jenkinsfile Outdated
notifyBuildResult(prComment: true)
notifyBuildResult(prComment: true,
githubIssue: isBranch() && currentBuild.currentResult != "SUCCESS",
githubLabels: 'Team:Elastic-Agent-Data-Plane')
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to change this GitHub label if required

@elasticmachine
Copy link
Contributor

elasticmachine commented Jun 22, 2022

💚 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: 2022-06-23T08:28:40.382+0000

  • Duration: 11 min 29 sec

Test stats 🧪

Test Results
Failed 0
Passed 304
Skipped 1
Total 305

🤖 GitHub comments

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

  • /test : Re-trigger the build.

.ci/Jenkinsfile Outdated Show resolved Hide resolved
Copy link
Contributor

@jlind23 jlind23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after updating the team label.

@v1v v1v merged commit a51ed0f into elastic:main Jun 23, 2022
@v1v v1v deleted the feature/add-github-reporting branch June 23, 2022 08:48
mergify bot pushed a commit that referenced this pull request Jun 23, 2022
mergify bot pushed a commit that referenced this pull request Jun 23, 2022
v1v added a commit that referenced this pull request Jun 23, 2022
(cherry picked from commit a51ed0f)

Co-authored-by: Victor Martinez <[email protected]>
v1v added a commit that referenced this pull request Jun 23, 2022
(cherry picked from commit a51ed0f)

Co-authored-by: Victor Martinez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.3.0 Automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants