2011-05-24 13:17:58 -05:00
|
|
|
*.gem
|
2011-05-25 15:39:53 -05:00
|
|
|
*.bundle
|
|
|
|
|
*.so
|
|
|
|
|
*.a
|
2012-05-09 20:10:21 -05:00
|
|
|
.rbx/
|
2011-05-24 13:17:58 -05:00
|
|
|
Gemfile.lock
|
2012-08-16 15:42:06 +02:00
|
|
|
Makefile
|
2011-05-24 13:17:58 -05:00
|
|
|
pkg/*
|
2011-05-25 15:39:53 -05:00
|
|
|
tmp/*
|
2011-05-25 16:04:12 -05:00
|
|
|
lib/libv8/build/*
|
2011-09-21 11:49:38 -05:00
|
|
|
lib/libv8/VERSION
|
2013-01-04 15:41:18 -06:00
|
|
|
/ext/libv8/.location.yml
|
framework for building binary gems
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
2015-06-27 02:36:57 +03:00
|
|
|
/release/**/libv8
|
|
|
|
|
/release/**/.vagrant
|
2017-07-18 22:19:40 +03:00
|
|
|
/release/**/.scaleway
|
2017-10-24 00:01:15 +03:00
|
|
|
/vendor/.gclient
|
|
|
|
|
/vendor/.gclient_entries
|
2020-07-17 17:08:14 -04:00
|
|
|
/vendor/.cipd
|
2017-10-24 00:01:15 +03:00
|
|
|
/vendor/v8/
|