[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13671 at 3/1/13 12:55 PM: ------------------------------------------------------------- A related change I did recently (in master branch only so far) is this: JBIDE-13672 Now, if the previous build's git revision (SHA) is the same as the current one, it won't bother to push the new bits to the staging/\{jobname\}/all/repo site, which means the composite site will not change, and therefore the downstream aggregation will not happen. This minimizes builds for the sake of building, but still allows us to rebuild/retest as a result of upstream changes (like a new target platform or a possible API change). So, should Base change, you can manually kick off Server to ensure everything still builds. But if the CODE in Server is unchanged, Server will not be *published*, only built & tested. You can scan the build logs for this message: {code} ======================================================================================================= GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with 'EXPORT skipRevisionCheckWhenPublishing=true; ======================================================================================================= {code} was (Author: nickboldt): A related change I did recently (in master branch only so far) is this: JBIDE-13672 Now, if the previous build's git revision (SHA) is the same as the current one, it won't bother to push the new bits to the staging/{jobname}/all/repo site, which means the composite site will not change, and therefore the downstream aggregation will not happen. This minimizes builds for the sake of building, but still allows us to rebuild/retest as a result of upstream changes (like a new target platform or a possible API change). So, should Base change, you can manually kick off Server to ensure everything still builds. But if the CODE in Server is unchanged, Server will not be *published*, only built & tested. You can scan the build logs for this message: {code} ======================================================================================================= GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with 'EXPORT skipRevisionCheckWhenPublishing=true; ======================================================================================================= {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira