VM creation sequence

[KrisThielemans]

We have an interesting circular thing going on now that the VM code is part of this repo. We need to tag the SIRF-SuperBuild before creating a VM, but we might need to fix things before tagging. The chain is

1. A new VM is created via
   

   SIRF-SuperBuild/VirtualBox/vagrant/Vagrantfile

   Line 99 in ec4b9c5

   config.vm.provision "shell", path: "../scripts/bootstrap_ubuntu.sh"

2. which calls UPDATE.sh (currently with the wrong branch)
   

   SIRF-SuperBuild/VirtualBox/scripts/bootstrap_ubuntu.sh

   Line 82 in ec4b9c5

   sudo -u $SIRFUSERNAME -H bash $userHOME/devel/SIRF-SuperBuild/VirtualBox/scripts/UPDATE.sh -t origin/vm_32

3. and UPDATE.sh defaults to using the latest tag
   

   SIRF-SuperBuild/VirtualBox/scripts/UPDATE.sh

   Lines 177 to 181 in ec4b9c5

   	if [ $1 = 'default' ]
   	then
   	# get the latest tag matching v
   	#SB_TAG=`git fetch; git for-each-ref refs/tags/v* --sort=-taggerdate --format='%(refname:short)' --count=1`
   	SB_TAG=`git tag | xargs -I@ git log --format=format:"%at @%n" -1 @ | sort | awk '{print $2}' | tail -1`

It seems that we need to create it first with a locally modified Vagrantfile that sets -t origin/master, do all the tests, tag, and then recreate.

@paskino any better ideas?

PS: I do think that UPDATE.sh still needs to default to using the latest tag, as this is what update_VM.sh will use.

[paskino]

I think this is what I generally do, anyway

[KrisThielemans]

item 2 "wrong tag" is no longer relevant.

SIRF-SuperBuild/VirtualBox/scripts/bootstrap_ubuntu.sh

Line 99 in 8ca5067

sudo -u $SIRFUSERNAME -H bash $userHOME/devel/SIRF-SuperBuild/VirtualBox/scripts/UPDATE.sh -s $*

[paskino]

We discussed that the SuperBuild code could be copied into the VM at creation time, similarly to how it is done in Docker.