Skip to content
This repository was archived by the owner on Dec 4, 2023. It is now read-only.

Commit 5c4508f

Browse files
committed
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
1 parent 07d6dc3 commit 5c4508f

3 files changed

Lines changed: 92 additions & 0 deletions

File tree

.gitignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,3 +10,5 @@ tmp/*
1010
lib/libv8/build/*
1111
lib/libv8/VERSION
1212
/ext/libv8/.location.yml
13+
/release/**/libv8
14+
/release/**/.vagrant

Rakefile

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,5 +91,22 @@ task :devkit do
9191
end
9292
end
9393

94+
namespace :build do
95+
['x86_64-linux'].each do |arch|
96+
desc "build binary gem for #{arch}"
97+
task arch do
98+
arch_dir = Pathname(__FILE__).dirname.join("release/#{arch}")
99+
Dir.chdir(arch_dir) do
100+
sh "vagrant up"
101+
sh "vagrant ssh -c 'cd /vagrant && rm -rf libv8 && git clone /libv8/.git libv8'"
102+
sh "vagrant ssh -c 'cd /vagrant/libv8 && bundle install --path vendor/bundle'"
103+
sh "vagrant ssh -c 'cd /vagrant/libv8 && bundle exec rake checkout binary'"
104+
sh "vagrant ssh -c 'cp /vagrant/libv8/pkg/*.gem /vagrant'"
105+
end
106+
end
107+
end
108+
109+
end
110+
94111
task :default => [:checkout, :compile, :spec]
95112
task :build => [:clean, :checkout]

release/x86_64-linux/Vagrantfile

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
# -*- mode: ruby -*-
2+
# vi: set ft=ruby :
3+
4+
# All Vagrant configuration is done below. The "2" in Vagrant.configure
5+
# configures the configuration version (we support older styles for
6+
# backwards compatibility). Please don't change it unless you know what
7+
# you're doing.
8+
Vagrant.configure(2) do |config|
9+
# The most common configuration options are documented and commented below.
10+
# For a complete reference, please see the online documentation at
11+
# https://docs.vagrantup.com.
12+
13+
# Every Vagrant development environment requires a box. You can search for
14+
# boxes at https://atlas.hashicorp.com/search.
15+
# https://atlas.hashicorp.com/quarkslab/boxes/debian-8.0-amd64
16+
config.vm.box = "quarkslab/debian-8.0-amd64"
17+
18+
# Disable automatic box update checking. If you disable this, then
19+
# boxes will only be checked for updates when the user runs
20+
# `vagrant box outdated`. This is not recommended.
21+
# config.vm.box_check_update = false
22+
23+
# Create a forwarded port mapping which allows access to a specific port
24+
# within the machine from a port on the host machine. In the example below,
25+
# accessing "localhost:8080" will access port 80 on the guest machine.
26+
# config.vm.network "forwarded_port", guest: 80, host: 8080
27+
28+
# Create a private network, which allows host-only access to the machine
29+
# using a specific IP.
30+
# config.vm.network "private_network", ip: "192.168.33.10"
31+
32+
# Create a public network, which generally matched to bridged network.
33+
# Bridged networks make the machine appear as another physical device on
34+
# your network.
35+
# config.vm.network "public_network"
36+
37+
# Share an additional folder to the guest VM. The first argument is
38+
# the path on the host to the actual folder. The second argument is
39+
# the path on the guest to mount the folder. And the optional third
40+
# argument is a set of non-required options.
41+
config.vm.synced_folder "../..", "/libv8"
42+
43+
# Provider-specific configuration so you can fine-tune various
44+
# backing providers for Vagrant. These expose provider-specific options.
45+
# Example for VirtualBox:
46+
#
47+
# config.vm.provider "virtualbox" do |vb|
48+
# # Display the VirtualBox GUI when booting the machine
49+
# vb.gui = true
50+
#
51+
# # Customize the amount of memory on the VM:
52+
# vb.memory = "1024"
53+
# end
54+
#
55+
# View the documentation for the provider you are using for more
56+
# information on available options.
57+
58+
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
59+
# such as FTP and Heroku are also available. See the documentation at
60+
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
61+
# config.push.define "atlas" do |push|
62+
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
63+
# end
64+
65+
# Enable provisioning with a shell script. Additional provisioners such as
66+
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
67+
# documentation for more information about their specific syntax and use.
68+
config.vm.provision "shell", inline: <<-SHELL
69+
sudo apt-get update
70+
sudo apt-get install -y build-essential git git-svn python ruby ruby-dev
71+
sudo gem install bundler
72+
SHELL
73+
end

0 commit comments

Comments
 (0)