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

Fail jenkins build unless ci-stats reports success #98846

Merged
merged 2 commits into from
Apr 30, 2021

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Apr 29, 2021

CI Stats has been writing the status of metrics to Kibana PRs for a while, which keeps people from merging those PRs, but it doesn't fail the actual Jenkins job which is confusing, and has lead to auto-merging allowing PRs with failed metrics (only been a problem on one backport so far).

This fixes the problem by adding a check to the Jenkins pipeline, not just when creating the comment but as a step in the pipeline that fails when ci-stats is not reporting a success (this might be because metrics are over a limit, or because of some other failure in the ci-stats service).

@spalger spalger added Team:Operations Team label for Operations Team v8.0.0 release_note:skip Skip the PR/issue when compiling release notes v7.14.0 v7.13.0 and removed Team:Operations Team label for Operations Team release_note:skip Skip the PR/issue when compiling release notes v7.13.0 v7.14.0 v8.0.0 labels Apr 29, 2021
@spalger spalger force-pushed the fix/ci-stats-reporting branch from 8f8233f to 822f1b4 Compare April 29, 2021 23:56
@spalger spalger changed the base branch from 7.13 to master April 29, 2021 23:56
@spalger spalger added release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team v7.13.0 v7.14.0 v8.0.0 labels Apr 29, 2021
@spalger spalger marked this pull request as ready for review April 29, 2021 23:58
@elasticmachine
Copy link
Contributor

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

@spalger spalger requested a review from brianseeders April 29, 2021 23:58
@spalger
Copy link
Contributor Author

spalger commented Apr 30, 2021

@elasticmachine merge upstream

Looks like the build from when master was merged but this PR was momentarily still based on 7.13 just finished, and the "mergeBase" was from 2019 when we forked 7.x.

Reminder to myself: need to make sure ci-stats is returning success: false when a merge base can't be found or any other non-success condition is met.

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@spalger spalger merged commit 246f4be into elastic:master Apr 30, 2021
@spalger spalger deleted the fix/ci-stats-reporting branch April 30, 2021 20:49
@spalger spalger added the auto-backport Deprecated - use backport:version if exact versions are needed label Apr 30, 2021
kibanamachine added a commit to kibanamachine/kibana that referenced this pull request Apr 30, 2021
@kibanamachine
Copy link
Contributor

💚 Backport successful

Status Branch Result
7.13
7.x

The backport PRs will be merged automatically after passing CI.

kibanamachine added a commit that referenced this pull request Apr 30, 2021
Co-authored-by: spalger <[email protected]>
Co-authored-by: Kibana Machine <[email protected]>

Co-authored-by: Spencer <[email protected]>
Co-authored-by: spalger <[email protected]>
kibanamachine added a commit that referenced this pull request Apr 30, 2021
Co-authored-by: spalger <[email protected]>
Co-authored-by: Kibana Machine <[email protected]>

Co-authored-by: Spencer <[email protected]>
Co-authored-by: spalger <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team v7.13.0 v7.14.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants