Here's a revert of the last change to move forward:
https://review.openstack.org/#/c/252063/
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284
On Tue, Dec 01, 2015 at 04:33:56PM +, Jeremy Stanley wrote:
> On 2015-12-01 09:22:38 +0100 (+0100), Andreas Jaeger wrote:
> > We recently merged changes to limit the running of jobs on
> > project-config to run only when a job is needed.
> >
> > But now we have a change [1] to data/* which is
On 2015-12-01 10:30:09 -0500 (-0500), Paul Belanger wrote:
[...]
> Maybe we need to build out some sort of test coverage for bindep,
> since it exposed missing coverage.
[...]
ITYM test coverage for the jenkins/data/bindep-fallback.txt file. I
was in fact thinking about writing this as recently as
On 2015-12-01 09:22:38 +0100 (+0100), Andreas Jaeger wrote:
> We recently merged changes to limit the running of jobs on
> project-config to run only when a job is needed.
>
> But now we have a change [1] to data/* which is not covered by any
> of the existing jobs and thus no job is run.
>
> Wha
On Tue, Dec 01, 2015 at 09:22:38AM +0100, Andreas Jaeger wrote:
> We recently merged changes to limit the running of jobs on project-config to
> run only when a job is needed.
>
> But now we have a change [1] to data/* which is not covered by any of the
> existing jobs and thus no job is run.
>
>
We recently merged changes to limit the running of jobs on
project-config to run only when a job is needed.
But now we have a change [1] to data/* which is not covered by any of
the existing jobs and thus no job is run.
What shall we do? Always run one of the existing jobs? Extend a job to
c
