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 problem since the rest of > > our build system already makes good use of cc.net. Is this going to be > > at all possible? > > > > It would be nice if it was possible to specify a task for user input, > > i.e. > > > > <userPrompt> > > <title>Release Label</title> > > <message>Enter the label name for this release</message> > > <envVar>ENVVAR_RELEASE_LABEL</envVar> > > <userPrompt> > > > > Of course this has to run client side with the result being provided > > server side. Now there is a challenge! > > > > HOW MANY users would find this sort of functionality useful? > > > > Regards, > > Shaun >
