[Anthill-pro] Changing lock during for multiple jobs

[Eric Minick]

Changing this will work for those jobs that are conflicting and are within
the same workflow - the workflow will get the lock rather than the
individual jobs.

To perform a mass update switching the setting on all projects, you could
connect t your database and apply the change there:
UPDATE WORKFLOW_DEFINITION_JOB_CONFIG SET IS_WORKFLOW_LOCK = 1

I would back-up my database before running any update commands.

-- Eric

On Mon, Nov 16, 2009 at 5:59 PM, Peter Steele <psteele at maxiscale.com> wrote:

> Yes, they do all use the same working directory (a network share). I have
> several workflows, each with several dozen build steps all set to use "Job"
> lock duration. This will be a very tedious exercise to change each one from
> Job to Workflow. Is there any way this can be automated?
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com [mailto:
> anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric Minick
> Sent: Monday, November 16, 2009 4:16 PM
> To: AnthillPro user and support list.
> Subject: Re: [Anthill-pro] "Enable Refresh" doesn't stick in 3.7.1
>
> This is more likely to be an issue where working directories are
> conflicting. Are all the jobs set to run in the same directory? If they're
> part of the same workflow you want to edit the workflow definition, edit
> each job's configuration and switch the lock type from job to workflow.
>
> - Eric
>
> On Mon, Nov 16, 2009 at 4:21 PM, Peter Steele <psteele at maxiscale.com>
> wrote:
>
> > Another problem I have discovered today is that even though I have my
> > build agents defined to run 5 jobs at a time, they seem to only be
> > running a single job. Is this a known issue?
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>