Re: [libvirt] [jenkins-ci PATCH 3/5] jobs: Rename {check_env} to {env}

2017-11-20 Thread Andrea Bolognani
On Mon, 2017-11-20 at 14:29 +0100, Pavel Hrdina wrote: > On Fri, Nov 17, 2017 at 07:26:10PM +0100, Andrea Bolognani wrote: > > There's no reason to have an environment which is tied, at least > > in name, to *-check-job only: having a local environment is > > something that can be useful for any ki

Re: [libvirt] [jenkins-ci PATCH 3/5] jobs: Rename {check_env} to {env}

2017-11-20 Thread Pavel Hrdina
On Fri, Nov 17, 2017 at 07:26:10PM +0100, Andrea Bolognani wrote: > There's no reason to have an environment which is tied, at least > in name, to *-check-job only: having a local environment is > something that can be useful for any kind of job, so it's better > to use a neutral name. My proposal

[libvirt] [jenkins-ci PATCH 3/5] jobs: Rename {check_env} to {env}

2017-11-17 Thread Andrea Bolognani
There's no reason to have an environment which is tied, at least in name, to *-check-job only: having a local environment is something that can be useful for any kind of job, so it's better to use a neutral name. Signed-off-by: Andrea Bolognani --- jobs/autotools.yaml | 2 +- jobs/defaults.y