Skip to content

Instantly share code, notes, and snippets.

@sickill
Last active Aug 29, 2015
Embed
What would you like to do?
#!/usr/local/bin/ruby
require 'bundler/setup'
require 'rugged'
repository_path = '/tmp/paraview'
rugged_repo = Rugged::Repository.new(repository_path)
from_sha = '732e37c7d2b1b88f2852615e1ccd736bd748a8ba'
to_sha = '629eddb612f5007c6bba0b6ad86a1189fd0a3bca'
ref = 'refs/heads/next'
walker = Rugged::Walker.new(rugged_repo)
walker.push(to_sha)
walker.hide(from_sha)
commits = walker.to_a # boom!
# commits = walker.map { |c| c } # boom too!
walker.reset
# A sample Gemfile
source "https://rubygems.org"
gem 'rugged', :git => 'https://github.com/libgit2/rugged.git', :branch => 'development', :submodules => true, :ref => 'fb28f860679f3a4bb29a9d1579f3b13754d81374'
GIT
remote: https://github.com/libgit2/rugged.git
revision: fb28f860679f3a4bb29a9d1579f3b13754d81374
ref: fb28f860679f3a4bb29a9d1579f3b13754d81374
branch: development
submodules: true
specs:
rugged (0.19.0)
GEM
remote: https://rubygems.org/
specs:
PLATFORMS
ruby
DEPENDENCIES
rugged!
#!/bin/bash
set -e
yum install -y wget cmake #ruby rubygems
# gem install bundler
if [[ ! -d ./ruby-install-0.4.3 ]]; then
wget -O ruby-install-0.4.3.tar.gz https://github.com/postmodern/ruby-install/archive/v0.4.3.tar.gz
tar -xzvf ruby-install-0.4.3.tar.gz
cd ruby-install-0.4.3/
sudo make install
fi
if [[ ! -x /usr/local/bin/ruby ]]; then
/usr/local/bin/ruby-install -i /usr/local/ ruby 2.0
fi
if [[ ! -x /usr/local/bin/bundle ]]; then
/usr/local/bin/gem install bundler
fi
if [[ ! -d /tmp/paraview ]]; then
git clone git://gitorious.org/kitware/paraview.git /tmp/paraview
fi
chown -R vagrant:vagrant /tmp/paraview
su vagrant -c "cd /vagrant && /usr/local/bin/bundle"
# -*- mode: ruby -*-
# vi: set ft=ruby :
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = "centos65"
config.vm.box_url = "https://github.com/2creatives/vagrant-centos/releases/download/v6.5.1/centos65-x86_64-20131205.box"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network "public_network"
# If true, then any SSH connections made will enable agent forwarding.
# Default value: false
# config.ssh.forward_agent = true
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider "virtualbox" do |vb|
# # Don't boot with headless mode
# vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
# vb.customize ["modifyvm", :id, "--memory", "1024"]
# end
#
# View the documentation for the provider you're using for more
# information on available options.
config.vm.provision "shell", :path => "provision.sh"
# Enable provisioning with CFEngine. CFEngine Community packages are
# automatically installed. For example, configure the host as a
# policy server and optionally a policy file to run:
#
# config.vm.provision "cfengine" do |cf|
# cf.am_policy_hub = true
# # cf.run_file = "motd.cf"
# end
#
# You can also configure and bootstrap a client to an existing
# policy server:
#
# config.vm.provision "cfengine" do |cf|
# cf.policy_server_address = "10.0.2.15"
# end
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file default.pp in the manifests_path directory.
#
# config.vm.provision "puppet" do |puppet|
# puppet.manifests_path = "manifests"
# puppet.manifest_file = "site.pp"
# end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision "chef_solo" do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
# end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision "chef_client" do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment