]
Nick Boldt updated JBDS-1361:
-----------------------------
Issue Type: Component Upgrade (was: Sub-task)
Need to track branch and revision # of contributed code
-------------------------------------------------------
Key: JBDS-1361
URL:
https://jira.jboss.org/browse/JBDS-1361
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Component Upgrade
Components: Build
Affects Versions: 4.0.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.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-desi...
http://download.jboss.org/jbosstools/builds/staging/pi4soa-3.1.x/logs/201...
Available:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta...
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta...
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: