[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-7444) Need to track branch and revision # of contributed code

[Nick Boldt (JIRA)]

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

Nick Boldt updated JBIDE-7444:
------------------------------

        Parent: JBIDE-6958
    Issue Type: Sub-task  (was: Feature Request)


> Need to track branch and revision # of contributed code
> -------------------------------------------------------
>
>                 Key: JBIDE-7444
>                 URL: https://jira.jboss.org/browse/JBIDE-7444
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: Build/Releng
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 3.2.0.Beta2
>
>
> Curerntly, I track SVN_REVISION when it's available in Hudson, which is generally not available because there is more than one checkout done per build. 
> Unavailable:
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-teiid-designer/logs/2010-10-05_15-20-41-H291.txt
> http://download.jboss.org/jbosstools/builds/staging/pi4soa-3.1.x/logs/2010-10-05_21-45-43-H10.txt
> Available:
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta1.nightly/logs/2010-10-06_15-31-05-H102-r25531.txt
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta1.aggregate/logs/2010-10-06_19-48-08-H202-r25503.txt
> 1. Therefore, instead of collecting this value from Hudson, we should perhaps scrape the build log to get the data needed.
> 2. Also, this information needs to be passed through to JBDS somehow as a new artifact after the build (perhaps attached to the buildResults page?)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira