|author||intrigeri <email@example.com>||2015-05-15 09:00:38 +0000|
|committer||intrigeri <firstname.lastname@example.org>||2015-05-15 09:04:59 +0000|
Don't modify files in the source tree before having possibly merged the base branch into it.
Previously, when building in Jenkins, we refreshed the wiki (twice) and translations before merging the base branch. As a result, we're seeing build failures with the "Your local changes to the following files would be overwritten by merge" error message. Let's now build the wiki and refresh translations only _after_ having merged the base branch, which makes more sense anyway: we want to include changes from the base branch into the wiki and translations. And while we're at it, let's refresh the wiki only once when building in Jenkins. Note that Vagrant builds will still build the wiki before setting up the ramdisk and running live-build: those builds don't merge the base branch anyway, so they can as well keep the wiki build caching mechanism, which is a nice optimization. Will-fix: #9406
Diffstat (limited to 'vagrant/provision')
1 files changed, 4 insertions, 1 deletions
diff --git a/vagrant/provision/assets/build-tails b/vagrant/provision/assets/build-tails
index 7cf2df3..3e06444 100755
@@ -91,7 +91,10 @@ install -m 0755 -d "$ARTIFACTS_DIR"
if [ "$TAILS_CLEAN_BUILD" ]; then
as_root_do lb clean --all
+if [ -z "$JENKINS_URL" ]; then
BUILD_DIR=$(mktemp -d /tmp/tails-build.XXXXXXXX)
if [ "$TAILS_RAM_BUILD" ]; then