[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:comment-tabpanel&focusedCommentId=12761347#comment-12761347 ] 

Nick Boldt edited comment on JBIDE-13672 at 3/15/13 9:10 AM:
-------------------------------------------------------------

Yes, because the whole point of checking the git revision is to see if it's been changed (and thus needs to be published) or unchanged (and thus does not need to be published).

So, if in my example above there were real changes in birt, you might see this:

{code}
#408 Mar 15 2:52pm
 * Rev: qrstuvwxyza (UNCHANGED)

#407 Mar 14 2:49pm
 * Rev: qrstuvwxyza

#406 Mar 14 2:36pm
 * Rev: abcdefghijkl (UNCHANGED)

#405 Mar 13 1:36pm
 * Rev: abcdefghijkl (UNCHANGED)

#404 Mar 13 1:36pm
 * Rev: abcdefghijkl
{code}
                
      was (Author: nickboldt):
    Yes, because the whole point of checking the git revision is to see if it's been changed (and thus needs to be published) or unchanged (and thus does not need to be published).

So, if in my example above there were real changes in birt, you might see this:

{code}
#408 Mar 15 2:52pm
 * Rev: qrstuvwxyza (UNCHANGED)

#407 Mar 14 2:49pm
 * Rev: qrstuvwxyza

#406 Mar 14 2:36pm
 * Rev: abcdefghijkl (UNCHANGED)

#405 Mar 13 1:36pm
 * Rev: abcdefghijkl (UNCHANGED)

#404 Mar 13 1:36pm
 * Rev: abcdefghijkl

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