History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-74
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Robin Shen
Reporter: Robin Shen
Votes: 2
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Be able to promote Subversion/Perforce CI build even if they are not tagged

Created: 02/May/06 06:05 PM   Updated: 31/Aug/06 07:02 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
From Dejan Radovic,

We have set up a "Continuous Integration" configuration which builds the sources at every commit. Also, we have set up an "Integration Testing" configuration which runs on a nightly basis and performs some extensive testing. So far, so good. Now if the tests fail, we would like to be able to run the "Integration Testing" on one of the previous "Continuous Integration" builds. We could do this by promoting a "CI" build to "IT", but promoting builds only works if the build has been tagged. And that's the issue. This means that you have to tag each "CI" build - which in turn increases the repository's revision number and polutes the commit logs with artificial entries - at every commit! We think that this is quite ugly and since we are using Subversion it seems unnecessary. It would suffice to know the revision number of the repository in order to reconstruct a "CI" build. How could we do this?

 All   Comments   Work Log   Change History      Sort Order:
No work has yet been logged on this issue.