Remove duplication, link to the API documentation more often, tweak wording, add `@UniqMartin` as a maintainer, note `@jacknagel`'s and `@adamv`'s significant past contributions to Homebrew, delete some outdated or unneeded documentation, add some missing `Formula` API. entries and simplify/improve `CONTRIBUTING.md`. Closes Homebrew/homebrew#46179. Closes Homebrew/homebrew#46618. Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
1.8 KiB
Brew Test Bot For Core Contributors
If a build has run and passed on brew test-bot then it can be used to quickly bottle formulae.
There are two types of Jenkins jobs you will interact with:
Homebrew Pull Requests
This job automatically builds any pull requests submitted to Homebrew/homebrew. On success or failure it updates the pull request status (see more details on the main Brew Test Bot wiki page). On a successful build it automatically uploads bottles.
Homebrew Testing
This job is manually triggered to run brew test-bot with user-specified parameters. On a successful build it automatically uploads bottles.
You can manually start this job with parameters to run brew test-bot with the same parameters. It's often useful to pass a pull request URL, a commit URL, a commit SHA-1 and/or formula names to have brew-test-bot test them, report the results and produce bottles.
Bottling
To pull and bottle a pull request with brew pull:
- Ensure the job has already completed successfully.
- Run
brew pull --bottle 12345where12345is the pull request number (or URL). If it complains about a missing URL withBrewTestBotin it then the bottles have not finished uploading yet; wait and try again later. - Run
git pushto push the commits.
To bottle a test build :
- Ensure the job has already completed successfully.
- Run
brew pull --bottle http://bot.brew.sh/job/Homebrew%20Testing/1234/wherehttp://bot.brew.sh/job/Homebrew%20Testing/1234/is the testing build URL in Jenkins. - Run
git pushto push the commits.