Hi, You can download the latest build from http://ccnetlive.thoughtworks.com/CCNet-builds/1.5.0/. These are "reasonably" stable as we have stopped adding new functionality and are working on bug fixes.
Alternately if you are waiting for an official release, we are hoping to have RC1 out by the end of the month. Craig ________________________________ From: Justin-Credible <[email protected]> To: ccnet-user <[email protected]> Sent: Tue, 19 January, 2010 7:22:52 AM Subject: [ccnet-user] Re: Scheduled build with parameters fails unless forced Awesome, thanks for your help! I assume this will be in the next release? I guess I'll use the workaround for now. On Jan 12, 12:52 am, "Craig Sutherland" <[email protected]> wrote: > I have managed to track down the differences and put in a fix for them. So > the defaults are no longer required on a dynamic parameter, instead if a > dynamic value does not have a default, it will attempt to get the default > from the parameter. If the parameter does not have a default (this is > optional), then an exception will be thrown. > > Hope this helps, > > Craig > > From: [email protected] [mailto:[email protected]] On > Behalf Of Craig Sutherland > Sent: Tuesday, 12 January 2010 9:20 p.m. > To: [email protected] > Subject: RE: [ccnet-user] Scheduled build with parameters fails unless > forced > > I've had a quick look at your config, the reason why this is happening is > because there are two types of default. > > The first is the default on the parameter. This default is what is sent to > the client when they do a force build, and currently that is the only time > it is used. > > The second is the dynamic value parameter, which is what is used when the > build actually runs. Originally this was an enforced parameter, but overtime > it has changed to become optional. This is where the problem is occurring - > one part of the code is still assuming this is a required parameter, while > another part isn't L > > I will dig a little deeper and see if I can find a resolution for this > problem, but for the moment the easy approach is to set a default on the > dynamic values - this can be done by adding a pipe and then the default > value, e.g. $[Major|0], $[CompileType|Debug], etc. > > I will let you know when I resolve the underlying problem. > > Craig > > From: [email protected] [mailto:[email protected]] On > Behalf Of Ruben Willems > Sent: Tuesday, 12 January 2010 8:30 p.m. > To: [email protected] > Subject: Re: [ccnet-user] Scheduled build with parameters fails unless > forced > > Hi > > I do not know the parameter code that well, but it sounds like when the > schedule trigger is fired, > the parameters are being ignored, and another default (I guesss "") is > taken, giving the error : > Input string was not in a correct format. > > with kind regards > Ruben Willems > > On Mon, Jan 11, 2010 at 6:17 PM, Justin-Credible > > <[email protected]> wrote: > > I have a project with parameters which builds fine when forced from > the dashboard. It also has a scheduleTrigger which always fails with > the following stack trace: > > System.FormatException: Input string was not in a correct format. > at System.Number.StringToNumber(String str, NumberStyles options, > NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) > > Full stack trace here:http://www.justin-credible.net/temp/CCNET-StackTrace.txt > > I don't understand why it works when I force the build and use > defaults and why it doesn't work when it runs by the scheduled > trigger. Any ideas? All of my numericParameters have defaults that are > numbers. > > Project is > here:http://www.justin-credible.net/temp/CCNET-ExampleProject.config.txt
