could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? ------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-13672 URL: https://issues.jboss.org/browse/JBIDE-13672 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.0.Alpha2 Attachments: jbide13672-proposed-markup.png, jbide13672-proposed-markup2.png Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). Sample files to check: http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site...