Hi If in step 1 you are talking about the triggers I specify in my cc.net configuration file, then I would expect that configuration without trigger block after force should go directly to step 3.1 (without doing step 2) If step1 is about some internal triggers then you should think about updating this behaviour on force build action, because I agree with Oliver: there are some situations I would like to do some stuff before I connect to source control. Or maybe you could introduce one more step 1.5 <PreSourceControl>
Regards, Vladas On 5 Rugp, 15:33, Ruben Willems <[email protected]> wrote: > Hi > > where in the docs did you find this, because it is indeed wrong. > > in the FAQ it is > correcthttp://confluence.public.thoughtworks.org/display/CCNET/FAQ > Operation flow of CCNet > > The exact sequence of operations is: > > 1) Wait for the triggers to awaken. > 2) Ask the source control system for a list of the modifications > since the last build. > 3) If any modifications were found or if the triggers said "force the > build": > 3.1) Generate a label for the build. > 3.2) Run the prebuild tasks in the order specified, failing > the build in case of error. > 3.3) Get the source code from the source control system. > 3.4) Run the build tasks in the order specified, failing the > build in case of error. > 3.5) If the repository should be labeled: > 3.5.1) Let the source control system apply the label. > 3.6) Run the publisher tasks. > 4) Go to 1. > > with kind regards > Ruben Willems > > > > On Tue, Aug 3, 2010 at 3:18 PM, OBones <[email protected]> wrote: > > Hello, > > > I have the following steps to create a release here: > > > Create a branch from a given URL > > Checkout a completely new working copy from the release branch > > Apply some changes so that the executable that will be built contains > > the svn revision number > > Commit those changes > > Build the executable for the release > > Tag the branch > > > I have thus configured a project in CruiseControl so that the source > > URL is given as a parameter and with a SVN source block that has its > > "trunkUrl" property set to the url of the later created release > > branch. > > The project is not scheduled to build automatically because it is the > > user who must specify the parameter. > > The first step is in "prebuild", the second should be taken care of by > > the SVN source block, and the remaining steps are in the tasks > > section. > > > This, however, does not work because CC checks the source for > > modification, thus calling SVN with the not yet created branch as the > > URL parameter. > > Considering that the build is forced, I would have thought that no > > "check for modification" would be needed, and as such that no calls be > > made to SVN before the prebuild tasks are even run. > > > To workaround this, I have disabled the SVN taks with autoGetSource > > set to False and gave it back the real trunk as the trunkUrl parameter > > value. > > > I don't know if this should be fixed or not, but I just wanted to warn > > people that despite what the documentation says, the prebuild tasks > > are not run before all source control process. The check for > > modification part calls the source control block before prebuild tasks > > are run. This is legitimate for scheduled tasks where you do not want > > those prebuild tasks to be run if there are no modifications. > > > But for forced builds, I would have thought that no check for > > modification was ever done. > > > Regards > > Olivier- Slėpti cituojamą tekstą - > > - Rodyti cituojamą tekstą -
