[jbosstools-issues] [JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBIDE-13672.
--------------------------------

    Resolution: Done


Jobs in both 41x/70x and master/trunk should now be able to force a publish even if nothing has changed since the last published SHA.
                
> 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
>
>
> 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/logs/GIT_REVISION.txt
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-sites.aggregate.site_41/logs/ALL_REVISIONS.txt

--
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