Comments (7)
documentation on using the command (rather than the test-bot system as a whole), other than --help - which does not provide high-level docs, just descriptions of each arg
This is all the documentation that's provided beyond https://docs.brew.sh/Brew-Test-Bot and https://docs.brew.sh/Brew-Test-Bot-For-Core-Contributors. We'll accept PRs to add any more and I'll answer questions on those PRs to fill in specific questions you have.
options for a custom upload script (i.e. to upload to somewhere that isn't bintray)
Instead of running brew test-bot --ci-upload
use the output bottles and JSON files to upload to the location of your choice.
a way to get both the locally-produced bottle filename, and the filename that it should be uploaded/stored as, without depending on implementation details
The output JSON generated by brew test-bot
contains this information.
from homebrew-test-bot.
The output JSON generated by brew test-bot contains this information.
Just checking: is this considered a stable public API?
from homebrew-test-bot.
It's simple enough that I don't see it needing to change so: yes, I guess so. It can be considered to follow the versioning of the rest of Homebrew so if there's deprecations they will be announced in the minor version release notes.
from homebrew-test-bot.
Thanks; I'll see if I can find someone who wants to pursue this, otherwise I'll probably take a look some time next year.
from homebrew-test-bot.
a way to get both the locally-produced bottle filename, and the filename that it should be uploaded/stored as, without depending on implementation details
The output JSON generated by brew test-bot contains this information.
I just ran into this issue since the 1.7.2 tag was made. I made some code that extracts the "filename that it should be uploaded/stored as" from the json and infer the "locally-produced bottle filename" from the name of the json file and changing the extension from json
to tar.gz
, since the "locally-produced bottle filename" isn't stored in the json.
from homebrew-test-bot.
I just ran into this issue since the 1.7.2 tag was made. I made some code that extracts the "filename that it should be uploaded/stored as" from the json and infer the "locally-produced bottle filename" from the name of the json file and changing the extension from json to tar.gz, since the "locally-produced bottle filename" isn't stored in the json.
@scpeters I think it would be good to make brew bottle --json
generate that information, what do you think? Would you be interested in submitting a PR to add it?
from homebrew-test-bot.
@MikeMcQuaid let me know what you think of Homebrew/brew#4736
from homebrew-test-bot.
Related Issues (20)
- Dependent formula is not build with `--build-dependents-from-source` when running test-bot HOT 3
- Error treating custom/tap/formula as a formula when there is a cask with the same name HOT 14
- Behavior change in building bottles against bottles from previous macOS versions HOT 13
- Annotations and ignore logic not working on Linux HOT 12
- Split bottling and testing a formula into separate steps HOT 13
- `git -C "${HOMEBREW_REPOSITORY}" clean` failed in `brew test-bot --only-cleanup-after` HOT 1
- Option to skip building unbottled dependents from source HOT 3
- Build bottles for arm64 HOT 1
- error in tap CI: brew link m4
- test-bot exiting on failure with success code HOT 2
- max number of concurrent jobs HOT 1
- Build failure due to deleted `etc` files from built dependencies HOT 1
- Don't skip if "has dependencies without compatible bottles" only affects `:build` dependencies HOT 6
- Bottles published but revision not merged HOT 5
- Cask was detected as formula with `--only-formulae` HOT 12
- `--only-formulae-detect` should work inside `merge_group` events HOT 1
- Tap CI failing on `brew test-bot --only-formulae` on Linux HOT 6
- gpsim 0.32.0 bottle issue HOT 5
- `brew test-bot --only-formulae` fails with a parsing error
- Errors resulting from `--new-formula` deprecation HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from homebrew-test-bot.