From f748c429212d2affa9d57bc9a5eee5487935d7b9 Mon Sep 17 00:00:00 2001 From: Paul Hinze Date: Mon, 25 Apr 2022 14:51:11 -0500 Subject: [PATCH] ci: Switch to static gem build names in non-shared dirs Having multiple different VMs building gems inside a shared dir was causing them to collide, making the second build always fail. --- test/vagrant-spec/scripts/ubuntu-install-vagrant.sh | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/test/vagrant-spec/scripts/ubuntu-install-vagrant.sh b/test/vagrant-spec/scripts/ubuntu-install-vagrant.sh index e7f959de3..2d6a07926 100755 --- a/test/vagrant-spec/scripts/ubuntu-install-vagrant.sh +++ b/test/vagrant-spec/scripts/ubuntu-install-vagrant.sh @@ -27,8 +27,8 @@ git config --global url."https://${HASHIBOT_USERNAME}:${HASHIBOT_TOKEN}@github.c gem install bundler -v "$(grep -A 1 "BUNDLED WITH" Gemfile.lock | tail -n 1)" make bundle install -gem build vagrant.gemspec -gem install vagrant*.gem +gem build -o /tmp/vagrant.gem vagrant.gemspec +gem install /tmp/vagrant.gem popd @@ -40,6 +40,6 @@ pushd vagrant-spec # necessary. Once this branch lands we can remove this line and build from main. git checkout vagrant-ruby -gem build vagrant-spec.gemspec -gem install vagrant-spec*.gem +gem build -o /tmp/vagrant-spec.gem vagrant-spec.gemspec +gem install /tmp/vagrant-spec.gem popd