Has anybody considered changing how check and gate jobs work such that
the tempest and grenade checks only run once the docs/pep8/unittests
jobs all succeed?
It seems like they complete so much quicker that folks can fix those
bugs before having to wait hours for the other jobs.
Thoughts, concern
Why developers need to wait for other jobs? Zuul shows current progress
well.
On Friday, December 6, 2013, Peter Portante wrote:
> Has anybody considered changing how check and gate jobs work such that
> the tempest and grenade checks only run once the docs/pep8/unittests
> jobs all succeed?
>
>
On Thu, Dec 5, 2013 at 2:37 PM, Peter Portante
wrote:
> Has anybody considered changing how check and gate jobs work such that
> the tempest and grenade checks only run once the docs/pep8/unittests
> jobs all succeed?
>
> It seems like they complete so much quicker that folks can fix those
> bugs
On Fri, Dec 6, 2013 at 9:32 AM, Clark Boylan wrote:
> On Thu, Dec 5, 2013 at 2:37 PM, Peter Portante
> wrote:
> > Has anybody considered changing how check and gate jobs work such that
> > the tempest and grenade checks only run once the docs/pep8/unittests
> > jobs all succeed?
> >
> > It seems
On Fri, Dec 6, 2013 at 9:15 AM, Sergey Lukjanov wrote:
> Why developers need to wait for other jobs? Zuul shows current progress
> well.
>
>
They don't need to wait, but it would free up resources for other jobs that
might
pass to get tested earlier.
>
> On Friday, December 6, 2013, Peter Portan
I like this idea.
Michael
On Thu, Dec 5, 2013 at 4:37 PM, Peter Portante
wrote:
> Has anybody considered changing how check and gate jobs work such that
> the tempest and grenade checks only run once the docs/pep8/unittests
> jobs all succeed?
>
> It seems like they complete so much quicker that
On Thu, Dec 5, 2013 at 3:33 PM, Christopher Yeoh wrote:
> On Fri, Dec 6, 2013 at 9:32 AM, Clark Boylan wrote:
>>
>> On Thu, Dec 5, 2013 at 2:37 PM, Peter Portante
>> wrote:
>> > Has anybody considered changing how check and gate jobs work such that
>> > the tempest and grenade checks only run on
I actually don't, for the reasons Clark brought up.
All this does is optimizes for people that don't run unit tests locally,
and make all the jobs take longer. Everything except the tempest jobs
should be easy to run locally.
So this would effectively penalize the people that do the right thing,
