[Anthill-pro] Preventing two builds from running at the sametime
on the same branch?
Ryan Smith
rws at urbancode.com
Mon Dec 31 14:31:19 CST 2007
Sam,
We just released 3.4.6 which contains a change that will allow your iterative jobs to run in parallel again. The work directory locking will recognize that the jobs are part of the same workflow and allow them to proceed.
Ryan Smith
Samuel Cameron wrote:
> Is there a way to allow jobs to use the same working directory in 3.4?
> Currently I have a job that is iterating 4 times that needs to use a
> working directory without changing what is in the working directory. I
> have this iterating job set to run in parallel, but because the working
> directory is locked, the effect is to run the jobs sequentially.
>
> Thanks,
> Sam Cameron
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric
> Minick
> Sent: Tuesday, December 18, 2007 3:06 PM
> To: AnthillPro user and support list.
> Subject: Re: [Anthill-pro] Preventing two builds from running at the
> sametime on the same branch?
>
> As an alternative, in the 3.4 versions Anthill will by default prevent
> any two jobs from executing in the same working directory on the same
> machine.
>
> -- Eric
>
> Steve Boone wrote:
>> Daniel,
>>
>> Glad to hear things are working for you. Have you tried using
>> lockable resources? Creating a lockable resource should solve this
>> scenario for you. It works by setting your workflows to use a
>> particular lock. Another workflow will not run, until the lock is
>> released. Once the lock is available, the second workflow will run.
>>
>> You can create your lockable resource from the System Tab, and then
>> incorporate it into your workflows, from the Administration Tab. Once
>
>> on the administration tab, click the workflow that you wish to have
>> the lock. Click the edit icon (the pencil) on the top left to edit
>> the lockable resource field.
>>
>> Let me know if you run into any problems.
>>
>> Cheers,
>> Steve Boone
>>
>>
>> On 12/18/07, *Daniel Kirsch* < Daniel.Kirsch at citrix.com
>> <mailto:Daniel.Kirsch at citrix.com>> wrote:
>>
>> Hello,
>>
>>
>>
>> I now have Continuous Integration running, thank you. Now I have
>> an issue with the possibility of two builds trying to run at the
>> same time, and the second build's clean step is removing or trying
>> to remove the binaries in order to sync clean.
>>
>>
>>
>> Is there an easy way to prevent a second build of the same
>> Workflow? Limit it to one at a time?
>>
>>
>>
>> Regards,
>>
>>
>>
>> Dan
>>
>>
>>
>>
>>
>> *Daniel Kirsch** *
>>
>> /Principal Software Development Engineer/
>>
>> Ardence, a Citrix Company - www.ardence.com
> <http://www.ardence.com/>
>> 266 2^nd Avenue
>>
>> Waltham, MA 02451
>>
>> 781.693.6326 Office
>>
>> 781.647.3999 Fax
>>
>> daniel.kirsch at citrix.com <mailto:daniel.kirsch at citrix.com>
>>
>>
>>
>>
>> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> <mailto: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
>>
> _______________________________________________
> 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
>
--
===========================================================
Ryan Smith. 2044 Euclid Ave., Suite 600
Lead Developer Cleveland, Ohio 44115
Urbancode, Inc.
email: rws at urbancode.com
web: www.urbancode.com phone: 216-858-9000
web: www.anthillpro.com fax: 216-858-9602
===========================================================
More information about the Anthill-pro
mailing list