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.

Sign up for GitHub

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

Jump to bottom

ci: create GitHub issue if build failure #31954

Merged
merged 9 commits into from
Jun 17, 2022
Merged

ci: create GitHub issue if build failure #31954

merged 9 commits into from
Jun 17, 2022

Conversation

v1v
Copy link
Member

@v1v v1v commented Jun 16, 2022 •
edited
Loading

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

Test

#31958 was created automatically

Related issues

Requires elastic/apm-pipeline-library#1731

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 16, 2022
@v1v v1v mentioned this pull request Jun 16, 2022
Merged
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jun 16, 2022 •
edited by jenkins-beats-ci bot
Loading

💚 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-16T14:08:55.458+0000

  • Duration: 74 min 26 sec

Test stats 🧪

Test Results
Failed 0
Passed 22268
Skipped 1937
Total 24205

💚 Flaky test report

Tests succeeded.

🤖 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.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify mergify bot assigned v1v Jun 16, 2022
v1v
v1v commented Jun 16, 2022
View reviewed changes
Jenkinsfile Outdated Show resolved Hide resolved
Jenkinsfile Outdated Show resolved Hide resolved
Jenkinsfile Outdated Show resolved Hide resolved
v1v
v1v commented Jun 16, 2022
View reviewed changes
Jenkinsfile Outdated Show resolved Hide resolved
Jenkinsfile Outdated Show resolved Hide resolved
@v1v v1v added Team:Automation Label for the Observability productivity team backport-v8.3.0 Automated backport with mergify backport-7.17 Automated backport to the 7.17 branch with mergify labels Jun 16, 2022
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 16, 2022
@v1v v1v requested review from cmacknz, jlind23 and a team June 16, 2022 14:10
@v1v v1v marked this pull request as ready for review June 16, 2022 14:10
@v1v v1v requested a review from a team as a code owner June 16, 2022 14:10
@v1v v1v merged commit 7102be4 into elastic:main Jun 17, 2022
@v1v v1v deleted the feature/notify-build-result-github-issue branch June 17, 2022 08:24
@v1v v1v added the backport-v8.2.0 Automated backport with mergify label Jun 17, 2022
@mergify mergify bot mentioned this pull request Jun 17, 2022
Merged
mergify bot pushed a commit that referenced this pull request Jun 17, 2022
@v1v @mergify
ci: create GitHub issue if build failure (#31954)
7d7a670 
(cherry picked from commit 7102be4)
mergify bot pushed a commit that referenced this pull request Jun 17, 2022
@v1v @mergify
ci: create GitHub issue if build failure (#31954)
afc3c5d 
(cherry picked from commit 7102be4)
@mergify mergify bot mentioned this pull request Jun 17, 2022
Merged
mergify bot pushed a commit that referenced this pull request Jun 17, 2022
@v1v @mergify
ci: create GitHub issue if build failure (#31954)
a6791e8 
(cherry picked from commit 7102be4)
@mergify mergify bot mentioned this pull request Jun 17, 2022
Merged
v1v pushed a commit that referenced this pull request Jun 17, 2022
@mergify
ci: create GitHub issue if build failure (#31954) (#31966)
8166bcb
v1v added a commit that referenced this pull request Jun 20, 2022
@mergify @v1v
ci: create GitHub issue if build failure (#31954) (#31968)
ab2b28e 
(cherry picked from commit 7102be4)

Co-authored-by: Victor Martinez <[email protected]>
v1v added a commit that referenced this pull request Jun 20, 2022
@mergify @v1v
ci: create GitHub issue if build failure (#31954) (#31967)
5dc1fac 
(cherry picked from commit 7102be4)

Co-authored-by: Victor Martinez <[email protected]>
This was referenced Jun 22, 2022
Merged
Merged
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
@mergify @v1v
ci: create GitHub issue if build failure (elastic#31954) (elastic#31967)
ffe1cba 
(cherry picked from commit f79397d)

Co-authored-by: Victor Martinez <[email protected]>
chrisberkhout pushed a commit that referenced this pull request Jun 1, 2023
@v1v @chrisberkhout
ci: create GitHub issue if build failure (#31954)
601ffc5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@cmacknz cmacknz cmacknz approved these changes

@cachedout cachedout cachedout approved these changes

@jlind23 jlind23 Awaiting requested review from jlind23

Assignees

@v1v v1v

Labels
backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.2.0 Automated backport with mergify backport-v8.3.0 Automated backport with mergify Team:Automation Label for the Observability productivity team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@v1v @elasticmachine @cachedout @cmacknz