<< Back to previous view

[QB-74] Be able to promote Subversion/Perforce CI build even if they are not tagged
Created: 02/May/06  Updated: 31/Aug/06

Status: Resolved
Project: QuickBuild
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Robin Shen Assigned To: Robin Shen
Resolution: Fixed Votes: 2
Remaining Estimate: Unknown Time Spent: Unknown
Original Estimate: Unknown


 Description   
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?

 Comments   
Comment by Olle Hallin [ 26/Jun/06 07:54 AM ]
This applies to Perforce as well.
Generated at Fri Oct 24 19:15:02 UTC 2025 using JIRA 189.