[
https://issues.jboss.org/browse/JBIDE-7444?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-7444:
-----------------------------------
publish.sh now collects status via Hudson XML API instead of scraping the build log. Much
more effective (except when it times out).
aggregate/site/build.xml now collects svn revision & build.properties files and
renames them uniquely so that aggregation is more feasible.
Next step -- pulling it all together into a single XML doc, then XSLT'ing it to HTML.
Need to track branch and revision # of contributed code
-------------------------------------------------------
Key: JBIDE-7444
URL:
https://issues.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
Priority: Minor
Fix For: 3.2.x, 3.3.x
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.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira