Bug: Dynamic Parameters: Prompt for input not displayed - http://jira.public.thoughtworks.org/browse/CCNET-1513
Feature Request: Dynamic Parameters: Range Parameter to allow initialisation from a file - http://jira.public.thoughtworks.org/browse/CCNET-1514 Dynamic Parameters: addition of Boolean parameter (Check Box) - http://jira.public.thoughtworks.org/browse/CCNET-1515 Dynamic Parameter: Range parameter should allow for return values that are not equal to the display name. - http://jira.public.thoughtworks.org/browse/CCNET-1516 Dynamic Parameters: Suggest renaming range parameter. - http://jira.public.thoughtworks.org/browse/CCNET-1517 Dynamic Parameters: Actual use of a retrieved value seems overly complex. - http://jira.public.thoughtworks.org/browse/CCNET-1518 Shaun :) On 12 May, 14:23, Daniel Nauck <[email protected]> wrote: > CinnamonDonkey schrieb: > > > What's the best way to provide feedback/bug reports? is there an > > official 1.5.0 sticky thread? on JIRA or email? > > JIRA and this google group is the best way to provide feedback. > > Daniel > > > Shaun > > > On 12 May, 11:25, "Craig & Sammi Sutherland" > > <[email protected]> wrote: > > >> Hi Shaun, > > >> As promised I've put together a quick write-up on how to use build > >> parameters:http://csut017.wordpress.com/2009/05/12/dynamic-build-parameters-some... > >> es/. > > >> As you've probably noticed, we don't support all the edit options you asked > >> for - but this is still a very new feature :-) We'll slowly add to it over > >> time and improve it, so feel free to send us any feedback. > > >> Craig > > >> -----Original Message----- > >> From: [email protected] [mailto:[email protected]] On > > >> Behalf Of CinnamonDonkey > >> Sent: Tuesday, 12 May 2009 7:05 p.m. > >> To: ccnet-user > >> Subject: [ccnet-user] Re: Build process requiring user input > > >> Thank you Craig, it's very much appreciated. I'd forgotten about your > >> blog :-). > > >> "...since this will definitely add value to CruiseControl.Net..." - it > >> definately will! This is a feature supported by Final Builder which > >> some of our teams have now moved over to (although after evaluation, > >> it is somewhat limited and they rested requests for feature updates). > > >> Personally I'm happier to stick with ccnet - it's progressing in > >> leaps'n'bounds! :D > > >> On 12 May, 01:44, Craig Sutherland <[email protected]> wrote: > > >>> Hi Shaun, > > >>> While we can't add this to the online documentation (yet), I have > >>> covered it in my blog. The following posts cover the dynamic > >>> parameters (including an example): > >>> *http://csut017.wordpress.com/2009/01/02/passing-dynamic-parameters-pa... > >>> *http://csut017.wordpress.com/2009/01/03/passing-dynamic-parameters-pa... > >>> *http://csut017.wordpress.com/2009/01/04/passing-dynamic-parameters-pa... > > >>> I'll see if I can write up some more examples for you as well. > > >>> Craig > > >>> On May 12, 12:43 am, CinnamonDonkey <[email protected]> > >>> wrote: > > >>>> Could someone perhaps cut'n'post a config snippet using input > >>>> parameters so that I can try it out. > > >>>> You could just email me your test config, should be enough for me to > >>>> get the gist of things :) > > >>>> On 11 May, 13:25, CinnamonDonkey <[email protected]> > >>>> wrote: > > >>>>> That's understandable Ruben. > > >>>>> On 11 May, 12:36, Ruben Willems <[email protected]> wrote: > > >>>>>> Hi > > >>>>>> the docs will be udpated as soon as 1.4.4 is out. > >>>>>> This is due to a condition in the release process, otherwise the > > >> 1.4.4 would > > >>>>>> have the docs of 1.5, > >>>>>> and that would cause confusion / errors. > > >>>>>> with kind regards > >>>>>> Ruben Willems > > >>>>>> On Mon, May 11, 2009 at 1:34 PM, CinnamonDonkey < > > >>>>>> [email protected]> wrote: > > >>>>>>> Hi Craig, > > >>>>>>> Is there any documentation for the new input stuff, I've had a > > >> hunt > > >>>>>>> around on the web site and in the source code. > > >>>>>>> But can't find much other than some new reflectors: > > >>>>>>> - textParameter > >>>>>>> - rangeParameter > >>>>>>> - numericParameter > > >>>>>>> I'll keep reading the code. > > >>>>>>> Good work you guys buy the way... looking at the source I can see > > >> all > > >>>>>>> sorts of new and wonderful things :) > > >>>>>>> On 11 May, 11:51, CinnamonDonkey <[email protected]> > >>>>>>> wrote: > > >>>>>>>> Found 1.5.0 here: > > >>>>>>>>http://ccnetlive.thoughtworks.com/CCNet-builds/1.5.0/ > > >>>>>>>> Going to have a play :) > > >>>>>>>> On 11 May, 11:38, Fyodor Koryazhkin <[email protected]> wrote: > > >>>>>>>>> Hi, > >>>>>>>>> I think that it would be very nice to make possible to > > >>>>>>> subscribe/unsubscribe > > >>>>>>>>> to mailing list through Dashboard or CCTray along with all > > >> mentioned > > >>>>>>>>> features above. > > >>>>>>>>> If it is possible to implement interactive build system it can > > >> cover > > >>>>>>> 90% of > > >>>>>>>>> people demands. > > >>>>>>>>> Fyodor. > > >>>>>>>>> On Mon, May 11, 2009 at 1:26 PM, CinnamonDonkey < > > >>>>>>>>> [email protected]> wrote: > > >>>>>>>>>> Hi Craig, > > >>>>>>>>>> Thanx for the quick response that's great news! It sounds > > >> pretty damn > > >>>>>>>>>> close to what we need ;-). Does it support, edit boxes, > > >> check boxes, > > >>>>>>>>>> radio buttons and listboxes or is that just asking for too > > >> much (some > > >>>>>>>>>> people are just never satisfied you know ;-). > > >>>>>>>>>> Is there a pre-built version of 1.5.0 I can tryout? > > >>>>>>>>>> For our use it would be most likely that the values would be > > >> passed > > >>>>>>> to > > >>>>>>>>>> an executable task as a parameter. i.e. MyExecutable.exe > > >>>>>>> --branch-name= > > >>>>>>>>>> $users_branch_name --scm-changlist="HEAD" > > >>>>>>>>>> Shaun. > > >>>>>>>>>> On 11 May, 11:01, "Craig & Sammi Sutherland" > >>>>>>>>>> <[email protected]> wrote: > > >>>>>>>>>>> We do have some good news for you Shaun, as part of 1.5.0 > > >> you can > > >>>>>>> now set > > >>>>>>>>>>> input parameters for a build. These parameters will be > > >> displayed to > > >>>>>>> the > > >>>>>>>>>> user > > >>>>>>>>>>> when they start a build (force build). > > >>>>>>>>>>> These parameters work both in the dashboard and CCTray and > > >> are set > > >>>>>>> up in > > >>>>>>>>>>> ccnet.config. And instead of needing an environment > > >> variable, they > > >>>>>>> can be > > >>>>>>>>>>> passed directly into the task (although you can still use > > >> it > > >>>>>>> together > > >>>>>>>>>> with > > >>>>>>>>>>> an environment variable if you really want.) > > >>>>>>>>>>> Does that sound like what you are after? > > >>>>>>>>>>> Craig > > >>>>>>>>>>> -----Original Message----- > >>>>>>>>>>> From: [email protected] [mailto: > > >>>>>>> [email protected]] > > >>>>>>>>>> On > > >>>>>>>>>>> Behalf Of CinnamonDonkey > >>>>>>>>>>> Sent: Monday, 11 May 2009 9:57 p.m. > >>>>>>>>>>> To: ccnet-user > >>>>>>>>>>> Subject: [ccnet-user] Build process requiring user input > > >>>>>>>>>>> Hi All, > > >>>>>>>>>>> I think this post probably belongs in the ccnet-dev group > > >> but I > > >>>>>>> figure > > >>>>>>>>>>> some other users may have input on this too (may have even > > >> solved > > >>>>>>> the > > >>>>>>>>>>> problem). > > >>>>>>>>>>> I have been asked to put together a build system with the > > >> following > > >>>>>>>>>>> requirements: > > >>>>>>>>>>> 1. The system is to be used to assemble the final release > > >> version > > >>>>>>> of > > >>>>>>>>>>> our products. > >>>>>>>>>>> 2. The system should create a new branch for the release > > >> in the > > >>>>>>> SCM. > > >>>>>>>>>>> 3. The user should be ASKED FIRST if they wish to rebuild > > >> an > > >>>>>>> existing > > >>>>>>>>>>> release branch or create a new release branch. > >>>>>>>>>>> 4. Existing release branches should be listed so that if > > >> the user > > >>>>>>>>>>> chooses to rebuild a branch then they can select the > > >> branch they > > >>>>>>> wish > > >>>>>>>>>>> to build. > >>>>>>>>>>> 5. The user should be allowed to specify a release label > > >> (branch > > >>>>>>> name) > > >>>>>>>>>>> when the user chooses to build a new release branch. > >>>>>>>>>>> 6. The build process should be automated. > >>>>>>>>>>> 7. The system should be accessible via a web browser. > > >>>>>>>>>>> Obviously the problem here is that User Input is required > > >> at the > > >>>>>>> start > > >>>>>>>>>>> of the process. > > >>>>>>>>>>> I'd really like to use CC.Net to solve this > > ... > > read more »
