Skip to content

Instantly share code, notes, and snippets.

$ make e2e_pilot
bin/gobuild.sh /home/vagrant/go/out/linux_amd64/release/istioctl istio.io/istio/pkg/version ./istioctl/cmd/istioctl
real 0m1.287s
user 0m0.620s
$ sudo make
vagrant destroy -f || true
==> default: VM not created. Moving on...
SCRIPT=vg-00-kubernetes.sh vagrant up --provision
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'debian/contrib-stretch64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: =9.4.0
==> default: Loading metadata for box 'debian/contrib-stretch64'
default: URL: https://vagrantcloud.com/debian/contrib-stretch64
@JimmyCYJ
JimmyCYJ / dep.md
Created February 24, 2018 00:42 — forked from subfuzion/dep.md
Concise guide to golang/dep

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include: