[ https://issues.jboss.org/browse/JBIDE-19950?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19950: ------------------------------------ Latest build is not publishing to the /updates/ location (just to /builds/) because when someone converted from *TWO* calls to rsync.sh to *ONE* call via mojo. Before (job config in jbosstools-integration-tests.aggregate_master/config.xml): {code} . ${WORKSPACE}/sources/publish/rsync.sh -s ${WORKSPACE}/sources/site/target/repository -t mars/snapshots/builds/${JOB_NAME}/${BUILD_ID}-B${BUILD_NUMBER}/all/repo . ${WORKSPACE}/sources/publish/rsync.sh -s ${WORKSPACE}/sources/site/target/repository -t mars/snapshots/updates/integration-tests/${jbosstools_site_stream} {code} After (mojo config): https://github.com/jbosstools/jbosstools-integration-tests/commit/7300d14...) But then someone removed that custom config, reverting to the default (which only pushes to /builds/, not to /updates/): https://github.com/jbosstools/jbosstools-integration-tests/commit/a33a265... So... I had a look at the console log, and both deploy-snapshot-updatesite and deploy-snapshot-build DID fire! So, no problem with the migration from sh to mojo. HOWEVER, in build B441... {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integration-tests.aggregate_master/441/console} [INFO] --- exec-maven-plugin:1.3.2:exec (deploy-snapshot-updatesite) @ site --- sftp> mkdir mars/snapshots/updates/integration-tests/4.3.mars rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/site/target/repository/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/integration-tests/4.3.mars/ {code} So, I believe the problem is that when we invoke maven from shell, the Jenkins variables aren't being passed in. Thus, since the integration-tests root pom still points to the Beta1-SNAPSHOT parent pom ([~mmalina] you need to move to Beta2 in master after you branch for Beta1x - see JBIDE-19933), it's using jbosstools_site_stream=*4.3.mars* (from maven), even though the value set in the job's parameters is *master*. I've tweaked the job to pass that value to maven on the commandline: {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository ${MAVEN_FLAGS} -Djbosstools_site_stream=${jbosstools_site_stream} {code} And I've kicked the job again. And now http://download.jboss.org/jbosstools/updates/nightly/integrationtests/mas... contains build B442. -- This message was sent by Atlassian JIRA (v6.3.15#6346)