[ https://issues.jboss.org/browse/JBIDE-21120?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21120: ------------------------------------ Reverted previous changes since Mickael's solution is easier/cleaner and more "maven-friendly". https://github.com/jbosstools/jbosstools-target-platforms/commits/4.60.x Here's the job config change: https://github.com/jbdevstudio/jbdevstudio-ci/commit/0349c99e890e1c1b06dd... Which results in this order of 8 steps (5 mvn, 3 bash): * checkout correct branch of code based on the input VERSION = 4.51.1.CR1-SNAPSHOT or 4.51.2.Beta1-SNAPSHOT or 4.60.0.Alpha1-SNAPSHOT ** git checkout ${branch} * push multiple .target to nexus ** mvn clean deploy -U -e -f multiple/pom.xml * resolve TP to get site + zip ** mvn install -U -Pmultiple2repo -e -f multiple/pom.xml * publish the full target platform + zip to dl.jb.o / ds.rh.c ** rsync ... * since unified .target depends on having published new bits to dl.jb.o / ds.rh.c, we can now build and deploy that ** mvn clean deploy -U -e -f unified/pom.xml * fetch dependencies for doing install tests ** org.jboss.tools.installation-tests:scripts ** org.jboss.tools.releng:jbosstools-releng-publish * now, do install tests (which might fail if the Eclipse JEE bundle contains incompatible versions of something in the TP (eg., we include a newer egit or m2e) ** getAndInstallEclipse.groovy ... ** installFromTarget.sh ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)