[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBDS-1361) Need to track branch and revision # of contributed code
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Fri Oct 8 03:04:39 EDT 2010
[ https://jira.jboss.org/browse/JBDS-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555990#action_12555990 ]
Nick Boldt edited comment on JBDS-1361 at 10/8/10 3:03 AM:
-----------------------------------------------------------
Scraper fixed and improved.
Now get data URL at REVISION such as this:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build@25619
or
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.Beta1/build@25636
or
http://anonsvn.jboss.org/repos/tdesigner/branches/7.1@1064
http://anonsvn.jboss.org/repos/jbosstools/trunk/build@25634
>From such generated files as:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta2.aggregate/logs/SVN_REVISION.txt
or
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta1.aggregate/logs/SVN_REVISION.txt
or
http://download.jboss.org/jbosstools/builds/staging/jbosstools-teiid-designer/logs/SVN_REVISION.txt
Next step: collating the data as part of JBDS results generation.
was (Author: nickboldt):
Scraper fixed and improved.
Now get data URL at REVISION such as this:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build@25619
For example:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta2.aggregate/logs/SVN_REVISION.txt
Nightly and Teiid builds still running.
Next step: collating the data as part of JBDS results generation.
> 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: Sub-task
> Components: Build
> Affects Versions: 4.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> 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
More information about the jbosstools-issues
mailing list