admin/brew
1
0
Fork 0
Code Issues Packages Projects Releases 6 Wiki Activity

Merge pull request #11903 from MikeMcQuaid/buildpulse

Browse Source 
Add BuildPulse links, docs
This commit is contained in:
Mike McQuaid 2021-08-24 19:07:22 +01:00 committed by GitHub
commit f469864423
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -90,6 +90,10 @@ Secure password storage and syncing is provided by [1Password for Teams](https:/
[![1Password](https://1password.com/img/redesign/press/logo.c757be5591a513da9c768f8b80829318.svg)](https://1password.com) [![1Password](https://1password.com/img/redesign/press/logo.c757be5591a513da9c768f8b80829318.svg)](https://1password.com)
Flaky test detection and tracking is provided by [BuildPulse](https://buildpulse.io/).
[![BuildPulse](https://user-images.githubusercontent.com/2988/130445500-96f44c87-e7dd-4da0-9877-7e5b1618e144.png)](https://buildpulse.io)
Homebrew is a member of the [Software Freedom Conservancy](https://sfconservancy.org). Homebrew is a member of the [Software Freedom Conservancy](https://sfconservancy.org).
[![Software Freedom Conservancy](https://sfconservancy.org/img/conservancy_64x64.png)](https://sfconservancy.org) [![Software Freedom Conservancy](https://sfconservancy.org/img/conservancy_64x64.png)](https://sfconservancy.org)

15
docs/Homebrew-brew-Maintainer-Guide.md
View File

@ -92,6 +92,21 @@ every line of code to have a test associated with it, especially when testing wo
integration test. For this reason, it's okay to merge PRs that fail the Codecov check if necessary, integration test. For this reason, it's okay to merge PRs that fail the Codecov check if necessary,
but this should be avoided if possible. but this should be avoided if possible.
### `brew tests` and BuildPulse
BuildPulse monitors CI jobs for every push to `Homebrew/brew` to detect flaky tests and track them over time. The
reports are available to Homebrew maintainers on [buildpulse.io](https://buildpulse.io/installations) and daily
summaries are published to [`#buildpulse-health`](https://machomebrew.slack.com/archives/C0268BSJBJ8) in Slack.
BuildPulse can be used as a guide to identify which flaky tests are causing the most disruption to the CI suite. To make
the biggest improvements to the reliability of the build, we can focus on the most disruptive flaky tests first (i.e.
the tests causing the most intermittent failures).
To help find the root cause for a particular flaky test, buildpulse.io provides links to the most recent CI job and
commit where the test failed and then passed with no change to the underlying code. You may want to check out the code
at that commit to attempt to reproduce the failure locally. You can also see the list of recent failures on
[buildpulse.io](https://buildpulse.io) to determine if the test always fails the same way.
## Manpages and shell completions ## Manpages and shell completions
Homebrew's manpages and shell completions are generated automatically by the `brew generate-man-completions` command. Homebrew's manpages and shell completions are generated automatically by the `brew generate-man-completions` command.