@Francis: If I'm reading that job correctly 'stacks/*/*.cfg' will work
as a value for the 'stacks' parameter and will deploy all stacks.
If that's correct can we use that as the default value ?
Yes, '*' does work for deploying multiple stacks. So 'stacks/*/*.cfg'
and 'stacks/head/*.cfg' are valid. I've added these as examples. I
prefer not to make this the default value because the deploy process
is not safe to do while cu2d jobs are running. I want whoever is
deploying to think about what they are doing until cu2d-update-stack
is updated to do this safely.
Also, can we make that job part of cu2d-config itself ? If only to not
have to
think too much about where we need to archive it otherwise ;)
We could add the job as a template in the cu2d-config branch, but I
would not configure the job to deploy itself.
Vincent
Hey Francis,
I think this job is running with -U, right? not -US.
How do you resetup the branch then, is the ps-jenkins bot used for launchpad
credential so that it fixes the bzr configurations?
It's using -US, the ps-jenkins credentials should be in effect. But I
haven't tested deploying a stack that needs to do this (don't we need
one that specifies a new project?).
