AtlasOfLivingAustralia / travis-build-configuration

travis-ci.org build configuration files shared/re-used among ALA projects
5 stars 8 forks source link

replace all hardcoded values (for example maven repo URLs) with env vars that can be sourced from one/single place #7

Open mbohun opened 9 years ago

mbohun commented 9 years ago

This approach is already implemented/tested for 3 projects, for example bie-webapp2 that is sourcing common shared env vars from ala-common.sh.
Move into ala-common.sh all shared:

This will allow for a simple comfortable change/update of vars/resources that have to be shared among all, resp. most ALA projects.

List of ALA github repos / .travis.yml files that need upgrading:

mbohun commented 8 years ago

Today we pretty much got forced into implementing this approach after all ALA grails builds started failing because a new version of GVM (we always install GVM from it's remote location at the start of each grails build) renamed their tools and property names:

--- test_build_old.sh   2015-09-17 14:07:42.000000000 +1000
+++ test_build.sh       2015-09-17 13:58:20.000000000 +1000
@@ -6,11 +6,11 @@
 chmod 775 ~/install_gvm.sh
 ~/install_gvm.sh

-echo "gvm_auto_answer=true" > ~/.gvm/etc/config
-source ~/.gvm/bin/gvm-init.sh
+echo "sdkman_auto_answer=true" > ~/.sdkman/etc/config
+source ~/.sdkman/bin/sdkman-init.sh

 GRAILS_VERSION=`grep '^app\.grails\.version=' ./application.properties | sed -e 's/^app\.grails\.version=//g'`
-gvm install grails $GRAILS_VERSION || true
+sdk install grails $GRAILS_VERSION || true

I implemented the new approach so far for userdetails