jenkins-build-all: improve detection of working buildserver VM

If I manually run some steps of the process, not all of the normal cruft
might be left behind.  I'm not really sure which of the multiple copies of
the images are actually required, but these both seem to work when present.
This commit is contained in:
Hans-Christoph Steiner 2017-12-14 10:41:02 +01:00
parent cc0399e740
commit 538d7155b4
1 changed files with 2 additions and 1 deletions

View File

@ -49,7 +49,8 @@ export VBOX_USER_HOME=$SETUP_WORKSPACE/VirtualBox
export VAGRANT_HOME=$SETUP_WORKSPACE/vagrant.d
# make sure we have the right buildserver paths and its ready for use
vagrant global-status | grep reproducible_setup_fdroid_build_environment
vagrant global-status \
| grep -F -e reproducible_setup_fdroid_build_environment -o -e fdroiddata/builder
# the way we handle jenkins slaves doesn't copy the workspace to the slaves
# so we need to "manually" clone the git repo here…