This sounds very similar to the dynamic build parameters work that was committed recently to the trunk (version 1.5.0.)
This works in a similar way - the dashboard makes an AJAX request to get a list of "build parameters". These build parameters are then passed through to a build integration. >From what I can see, there are a couple of differences: 1. The trunk version does not store the parameters - these are passed through directly to the server 2. The trunk version allows parameters to be passed to any task A couple of other items that weren't mentioned, but are included in the trunk version: . The configuration for these parameters is stored in ccnet.config - not sure where you store the configuration for these items (are they dynamic?) . The parameters also work in CCTray Does this sound like what you have done? Craig From: [email protected] [mailto:[email protected]] On Behalf Of Ruben Willems Sent: Saturday, 9 May 2009 7:31 a.m. To: [email protected] Subject: [ccnet-user] Re: Corporate Environment - Deploying to various environments nice updates, some of these are being worked on already, but your approach sure has some neat touches ;-) On Fri, May 8, 2009 at 8:55 PM, MKCline <[email protected]> wrote: My 'hack'/'customizations' are based on 1.4.2.14. The added security in 1.5 may be something that could be leveraged for further purposes. My 'hacks' are all loosely tied into the system and it basically breaks down like this: Some alterations to the ProjectGrid.vm -- To add some drop downs and buttons which call a webservice via AJAX A webservice page that is hosted and stores my data in a database (could have been a flat file, serialized dataset or something, but chose quick and dirty db table) Then a plugin library for ccnet to do some other dirty work for me. Most critical is an msbuild wrapper that gets the settings that were set via the front-end and then passes them to MSBuild when it runs. This allows me to have a 'Binary Deploy' target that takes in a version and an environment from MSBuild perspective, but since this is data driven I have a single CCNET build -- Binary Deploy. I can send this any combination of version/environment from the front-end.
