This repository was archived by the owner on Dec 4, 2023. It is now read-only.
Conversation
I'm tired of our releases getting held up because building the binaries is such a yak shave. We're in dire need of some automation. I tried spiking some things out with Docker, but for the time being, it was easier to just go with Vagrant. Currently, our release process for binary gems involves 1. a source release at an even point (e.g. 3.16.14.8) 2. a version bump to serve as the basis for binary releases 3. a mish-mash of gem builds and pushes for osx, linux, freebsd, etc... In order to make things eaiser for us to manage these binary builds, I'm proposing a standardized build using Vagrant. For each supported release, a Vagrant file goes into /release/<arch>/Vagrantfile The vagrantfile is responsible for provisioning a modern ruby toolchain including bundler, git, git-svn, ruby and ruby source and headers. It should also clone the libv8 source into the /libv8 This can then be used to build the binary gem for that platform. This PR includes the Vagrantfile for x86_64-linux
Collaborator
|
👍 |
cowboyd
added a commit
that referenced
this pull request
Jun 30, 2015
framework for building binary gems
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm tired of our releases getting held up because building the binaries
is such a yak shave. We're in dire need of some automation. I tried
spiking some things out with Docker, but for the time being, it was
easier to just go with Vagrant.
Currently, our release process for binary gems involves
In order to make things eaiser for us to manage these binary builds, I'm
proposing a standardized build using Vagrant. For each supported
release, a Vagrant file goes into /release//Vagrantfile
The vagrantfile is responsible for provisioning a modern
ruby toolchain including bundler, git, git-svn, ruby and ruby source and
headers.
It should also clone the libv8 source into the /libv8
This can then be used to build the binary gem for that platform.
This PR includes the Vagrantfile for x86_64-linux