canonical-ci-engineering team mailing list archive

[Vincent Ladeuil <vila+ci@xxxxxxxxxxxxx>]

>>>>> Francis Ginther <francis.ginther@xxxxxxxxxxxxx> writes:

    >>> @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.

Ack.

    >>> 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,

That would be great as a first step to ensure that piece of knowledge is
properly tracked and shared.

    > but I would not configure the job to deploy itself.

Why ? I realize it may seem a bit weird to always deploy that job each
time it's used but what are the risks ? Losing changes made only in
jenkins ? I'm tempted to say it's a good idea ;-)

Anyway, as long as we have that job definition in more than one place,
I'd be happy enough ;)

    Vincent