-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update homebrew formulae and bottles from release.py #47
Comments
Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero). We should be able to know if there is a brew formula by going into the homebrew-simulation github repo (using github API) and use the PACKAGE_NAME passed to release.py when running the script (sdformat2, gazebo6, ignition-math2), right? If there is no a better way, hosting the brew metadata in the release repo is perfectly fine, but if can do it automatically, sounds better to me. |
Original comment by Steve Peters (Bitbucket: Steven Peters). Yeah, we should be able to do it automatically |
Original comment by Steve Peters (Bitbucket: Steven Peters). We should also build and upload homebrew bottles (binaries) |
Original comment by Steve Peters (Bitbucket: Steven Peters). Bottles requested in this issue: |
Original comment by Steve Peters (Bitbucket: Steven Peters). To build a formula (ogre for example):
This spits out a tarball in the current working directory and some text that needs to be added to the formula (the |
Original comment by Steve Peters (Bitbucket: Steven Peters). The following job should test the use of the ogre bottle when it actually runs: |
Original comment by Steve Peters (Bitbucket: Steven Peters). I've been peeking into the brew test bot, which builds bottles and uploads them to a repository, then pushes the bottle signatures to a fork with tags. Look at all the tags: Apparently |
Original comment by Steve Peters (Bitbucket: Steven Peters). pull request #125 is a start |
Original comment by Steve Peters (Bitbucket: Steven Peters).
|
Original comment by Steve Peters (Bitbucket: Steven Peters). So the following currently works:
the bottle build also triggers a bottle pr hash updater job, but that isn't yet working I'm looking at it right now. |
Original comment by Steve Peters (Bitbucket: Steven Peters). Note that the |
Original comment by Steve Peters (Bitbucket: Steven Peters). release.py will now create a homebrew pull request, build a bottle for yosemite, and update the pull request with a checksum more work is needed to support bottles for multiple versions of osx |
Original comment by Steve Peters (Bitbucket: Steven Peters).
|
Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters).
It would be nice to update the homebrew formulae as part of the release process with release.py. Here's an example of a formula update: an updated tarball link and an updated checksum.
We would need to figure out which repositories have homebrew formulae. Perhaps we can put a file in the
-release
repo with the name of the homebrew formula?The result should be a pull request to https://github.com/osrf/homebrew-simulation
The text was updated successfully, but these errors were encountered: