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] In-progress PR notifications #71454

Closed
brianseeders opened this issue Jul 13, 2020 · 2 comments · Fixed by #72211
Closed

[CI] In-progress PR notifications #71454

brianseeders opened this issue Jul 13, 2020 · 2 comments · Fixed by #72211
Assignees
Labels
Feature:CI Continuous integration release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team

Comments

@brianseeders
Copy link
Contributor

brianseeders commented Jul 13, 2020

Similar to #70881, it should be pretty easy to:

  • Create a new, "in-progress" PR comment on the first failed build step
  • Update the PR comment on each subsequent failure
  • When the build is finished, post a new comment as usual or update the in-progress one for this build
@brianseeders brianseeders added Feature:CI Continuous integration release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team labels Jul 13, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@brianseeders
Copy link
Contributor Author

Thinking about it a little more, it would be really difficult to make this work automatically for any step in Jenkins that generates an error, but it still seems easy and useful to add to a few key places. E.g. anything that executes via runbld, which is pretty much everything that matters

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:CI Continuous integration release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants