[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21012: ------------------------------------ So to recap, these changes are needed to the site/pom.xml and job config: {quote} 1. define BUILD_NUMBER and timestamp for when building locally 2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/${project.name}-${project.version}.zip into the Nexus deployment. 3. set <classifier>${BUILD_ALIAS}</classifier> if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54 {code} - $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} + $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER} {code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156 One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :( To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)