Hi! I think there are two separate things here. The first is the server part - that is, put a IfModificationExists build in the queue, which is not emitted by an interval trigger. The second thing is how to tell the server to do that. As far as I can see there are four different ways to tell the server what to do - the dashboard, the CCTray utility, the CCCmd executable (all triggered by user interaction) and as task in a configuration block (trigger by script). For the CCTray, a dialog box would by very nice indeed. Especially if the dialog box displayed the typical (or last successful) build time and provides a means to cancel the dialog box. Other options could be a separate context menu entry, or (in the cctray config) to switch the default "force build mode", and chose the other one or display the dialog box when the shift key is pressed when clicking the context menu.
Markus ________________________________ Von: [email protected] im Auftrag von Ruben Willems Gesendet: So 03.10.2010 09:15 An: [email protected] Betreff: Re: [ccnet-user] Trigger IfModificationExists with CCCmd Hi it's indeed a bit tricky maybe something is possible with a dynamic parameter. when the user presses the force build, ask a 'value' ° only build when there are mods (or previous is bad) ° just force the build, regardless of any condition I think this covers most needs, what do you think of this idea? with kind regards Ruben Willems On Fri, Oct 1, 2010 at 11:21 PM, Phil Sayers <[email protected]> wrote: Something like.. <forcebuild> <NoModifications allowed=false/> <Modifications allowed=false/> <PriorBuildFail allowed=true/> <PriorBuildSuccess allowed=true/> (this one seems kinda silly to me) <AlreadyQueued allowed=false/> <NotAlreadyQueued allowed=false/> (this one seems kinda silly to me) </forcebuild> I suppose this could be condensed into... <forcebuild NoModifications=false Modifications=true PriorBuildFail=true PriorBuildSuccess=true AlreadyQueued=false NotAlreadyQueued=false/> There would probably have to be some validation too to make sure that we do not create a situation where it is impossible for a build to occur. I could see this getting out of hand pretty quickly.... So many possible conditions or combinations of conditions you may want to evaluate as part of the decision to ignore a forcebuild request. From: [email protected] [mailto:[email protected]] On Behalf Of Ruben Willems Sent: Friday, October 01, 2010 2:47 PM To: [email protected] Subject: Re: [ccnet-user] Trigger IfModificationExists with CCCmd Hi intresting idea :-) but suppose the trigger is defined as <forceBuild when="OnlyModificationsDetected" /> and the build fails because the source control is bad / database is bad / network is bad, anything but a bad checkin how would can you 'reforce' a build? pressing the force build button will not do anything, because there are no changes done or should we alter the condition to : <forceBuild when="OnlyModificationsDetectedOrPreviousBuildIsBad" /> a shorter settings name is welcome, but this shows the idea :-) with kind regards Ruben Willems On Fri, Oct 1, 2010 at 9:48 AM, Essl, Markus <[email protected]> wrote: Hi! Yes, that is exactly what I need. It happens again and again that I think - "uh, oh, I clicked on the wrong project to force build". While it is sometimes necessary that the existing code gets compiled again, so that i have a fresh set of binaries without sourcecode changes, it is more often the case that I need a build because of source code changes. Since the build process is really long, and I need to wait until all developers have commited their work, I usually have that kind of project on a "manual build" mode, and build them when necessary. (and yes, I have some projects that run on an 2 minute interval and on 2 hour interval, I know how to do that). Markus ________________________________ Von: [email protected] im Auftrag von Phil Sayers Gesendet: Do 30.09.2010 17:34 An: [email protected] Betreff: RE: [ccnet-user] Trigger IfModificationExists with CCCmd >Hello! > >This is a follow up to my last question, no rephrased to possible get a better answer. Is it possible to queue a build >(with CCCmd for instance) that is not a "ForceBuild" but a "IfModifactionExists" build? > >Markus > To frame the question a little differently.... You are looking for a way for a "ForceBuild" (ForceBuild being a user requested build) to be ignored if there are no modifications detected? Maybe this could be supported with something in the triggers block of a project.. <forceBuild when="OnlyModificationsDetected" /> <forceBuild when="Always" /> <--default I would be interested in this functionality too. bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz | FN 247859z | ATU58011225 | Gerichtsstand Graz bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 195426t | ATU49978207 | Gerichtsstand Wien Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311, 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz bit schulungscenter Nfg GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 264297 y | ATU61831566 | Gerichtsstand Graz bit management Beratung GesmbH | Kaerntner Strasse 311, 8054 Graz | FN 247859z | ATU58011225 | Gerichtsstand Graz bit media e-learning solution GmbH & Co KG | Kaerntner Strasse 311, 8054 Graz | FN 195426t | ATU49978207 | Gerichtsstand Wien Unternehmensberatung bit consulting GmbH | Kaerntner Strasse 311, 8054 Graz | FN 196369d | ATU49853109 | Gerichtsstand Graz
<<winmail.dat>>
