[Anthill-pro] Stop the queing of builds - agent selection script
Eric Minick
etm at urbancode.com
Tue Sep 11 14:49:23 CDT 2007
The trick is that what you'd really want is a script that removes the
one that's in the queue already and replaces it with the new request. I
imagine it's doable, but if we can find a solid solution that doesn't
require creative scripting, I would prefer the more stable approach.
-- Eric
Curtis Yanko wrote:
> Is there a scriptable way to check if a job is in the queue? That workflow
> could trigger the other based on success or failure???
>
> Curtis Yanko
> UnitedHealth Group IT
> Computer Services - AIS
> Source->Build->Deploy
> curt_yanko at uhc.com
> 450 Columbus Blvd
> CT028-06SA
> Hartford, CT 06103
> work: 860.702.9059
> cell: 860.881.2050
>
>
>
>
> Eric Minick <etm at urbancode.com>
> Sent by: anthill-pro-bounces at caladin.urbancode.com
> 09/11/2007 01:22 PM
> Please respond to
> "AnthillPro user and support list." <anthill-pro at caladin.urbancode.com>
>
>
> To
> "AnthillPro user and support list." <anthill-pro at caladin.urbancode.com>
> cc
>
> Subject
> Re: [Anthill-pro] Stop the queing of builds - agent selection script
>
>
>
>
>
>
> Andrew,
>
> I'd even go with a simple 90 or 100 minute schedule that isn't forced.
> Every hour and a half a build is triggered if there were any changes
> since the last window. If not, the build system goes quite for that time.
>
> I hear what you're saying though, it would be a healthy thing if there
> was more consolidation of builds. There's a tiny amount of that going on
> right now - particularly in the resolution of complex dependency trees,
> but it's something we could definitely build out some more.
>
> The rules for when to consolidate can get complex fast (as a near worst
> case, imagine a build that is configured to do something different
> depending on the user that triggers it). We've been very cautious about
> doing too much consolidation to date, but you're not the only one who
> has seen the oversaturated build queue issue and if we can address it
> without breaking stuff, we will.
>
> Regards,
>
> Eric
>
> Curtis Yanko wrote:
>
>> With the aid of a free-trade French Roast and a Chocolate Croissant I am
>>
>
>
>> ready to tackle the world (but that may be the caffeine talking!)
>>
>> I see your dilemma now. Perhaps repository triggered builds aren't the
>>
> way
>
>> to go then.Perhaps a Cron style (or two actually) with more modest quiet
>>
>
>
>> periods of 5 minutes or so.
>>
>> Curtis Yanko
>> UnitedHealth Group IT
>> Computer Services - AIS
>> Source->Build->Deploy
>> curt_yanko at uhc.com
>> 450 Columbus Blvd
>> CT028-06SA
>> Hartford, CT 06103
>> work: 860.702.9059
>> cell: 860.881.2050
>>
>>
>>
>>
>> "Baker, Andrew" <abaker at rsasecurity.com>
>> Sent by: anthill-pro-bounces at caladin.urbancode.com
>> 09/11/2007 09:37 AM
>> Please respond to
>> "AnthillPro user and support list." <anthill-pro at caladin.urbancode.com>
>>
>>
>> To
>> "AnthillPro user and support list." <anthill-pro at caladin.urbancode.com>
>> cc
>>
>> Subject
>> RE: [Anthill-pro] Stop the queing of builds - agent selection script
>>
>>
>>
>>
>>
>>
>> The problem with upping the quiet period is that even our quick build
>>
> and
>
>> test take 90 minutes (overnight builds can take up to 8 hours), so it is
>>
>
>
>> very unlikely we will ever get a time where no-one checks in for 90
>> minutes, so this queue will always be the case. Upping the quiet period
>>
>
>
>> lowers the number of builds, but it is still a problem. Even if we make
>>
>
>
>> it very large we can get queued up builds some times and none others ?
>> using too long a quiet period may get no builds for hours.
>>
>> Hopefully you have had your coffee now.
>>
>> Andrew
>>
>> Andrew Baker | Quality Manager | +61 7 3227 4462| abaker at rsa.com
>>
>>
>> From: anthill-pro-bounces at caladin.urbancode.com
>> [mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Curtis
>> Yanko
>> Sent: Tuesday, 11 September 2007 11:06 PM
>> To: AnthillPro user and support list.
>> Subject: Re: [Anthill-pro] Stop the queing of builds - agent selection
>> script
>>
>>
>> Can you just up the length of the quiet period?
>>
>> Curtis Yanko
>> UnitedHealth Group IT
>> Computer Services - AIS
>> Source->Build->Deploy
>> curt_yanko at uhc.com
>> 450 Columbus Blvd
>> CT028-06SA
>> Hartford, CT 06103
>> work: 860.702.9059
>> cell: 860.881.2050
>>
>>
>>
>>
>> "Baker, Andrew" <abaker at rsasecurity.com>
>> Sent by: anthill-pro-bounces at caladin.urbancode.com
>> 09/11/2007 02:34 AM
>>
>>
>> Please respond to
>> "AnthillPro user and support list." <anthill-pro at caladin.urbancode.com>
>>
>>
>>
>> To
>> "AnthillPro user and support list." <anthill-pro at caladin.urbancode.com>,
>>
>
>
>> <support at urbancode.com>
>> cc
>> "Watts, Kate" <kwatts at rsasecurity.com>, "Parkinson, Sean"
>> <sparkinson at rsasecurity.com>
>> Subject
>> [Anthill-pro] Stop the queing of builds - agent selection script
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> We have a number of builds which queue up over time. We are building C
>> programs with advanced cryptography tests so they take a while to
>>
> execute.
>
>> We are finding that even with a quiet period we get multiple builds
>> waiting for a build agent.
>>
>> Example:
>> Running Q1 Q2 Q3 Q4 Q5
>>
>> We really just want the latest check in to kick off when the current
>>
> build
>
>> completes, so in the example above, when the running job finishes we
>>
> want
>
>> the queued item listed at Q5 to execute with the Q1 through Q4 to just
>> fail as a build request (or just disappear would be nice)
>>
>> I don?t know how best to do this, but possibly an event trigger
>>
> utilizing
>
>> a specialist script?
>>
>> Any help appreciated
>>
>> Andrew
>> Andrew Baker | Quality Manager | +61 7 3227 4462| abaker at rsa.com
>>
>> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>
>>
>>
>> This e-mail, including attachments, may include confidential and/or
>> proprietary information, and may be used only by the person or entity to
>>
>
>
>> which it is addressed. If the reader of this e-mail is not the intended
>> recipient or his or her authorized agent, the reader is hereby notified
>> that any dissemination, distribution or copying of this e-mail is
>> prohibited. If you have received this e-mail in error, please notify the
>>
>
>
>> sender by replying to this message and delete this e-mail immediately.
>> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>
>>
>>
>> This e-mail, including attachments, may include confidential and/or
>> proprietary information, and may be used only by the person or entity to
>>
>
>
>> which it is addressed. If the reader of this e-mail is not the intended
>> recipient or his or her authorized agent, the reader is hereby notified
>> that any dissemination, distribution or copying of this e-mail is
>> prohibited. If you have received this e-mail in error, please notify the
>>
>
>
>> sender by replying to this message and delete this e-mail immediately.
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>
>>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity to
> which it is addressed. If the reader of this e-mail is not the intended
> recipient or his or her authorized agent, the reader is hereby notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify the
> sender by replying to this message and delete this e-mail immediately.
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
More information about the Anthill-pro
mailing list