You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Stephen Mallette <sp...@gmail.com> on 2019/06/07 19:44:51 UTC

Travis Job Naming

I've long been tired of seeing a failing job in Travis and then just seeing
a red "X" and a job number and then having to scroll through the log output
to figure out which particular build job failed. was it python? was it
.NET? was it just regular ol' mvn clean install?

Well, I've managed to make some improvements and figured out how to stage
test runs into groups and then assign names to them - here's an example of
what it looks like now:

https://travis-ci.org/apache/tinkerpop/builds/542862332

Now, you see an "X", you immediately know what tanked. excellent

Re: Travis Job Naming

Posted by Stephen Mallette <sp...@gmail.com>.
Yeah...I was aware of the loss of complete parallelism I guess. Logically,
if the first stage failed then the second stage wasn't worth even trying
with similar logic for the third. But, perhaps it's all just a single
"Testing" stage. I'll change it.

On Mon, Jun 10, 2019 at 4:36 AM Jorge Bay Gondra <jo...@gmail.com>
wrote:

> Oh looks way cleaner! Thanks!
>
> One thing we lost with this layout is the ability to run multiple test
> groups in parallel, build time went from ~42mins
> <https://travis-ci.org/apache/tinkerpop/builds/534940067> to 1h19m
> <https://travis-ci.org/apache/tinkerpop/builds/543397816>.
>
> The underlying reason is that TravisCI runs one stage after another
> sequentially. We could group them into the same stage to get them to start
> in parallel.
>
> On Fri, Jun 7, 2019 at 9:44 PM Stephen Mallette <sp...@gmail.com>
> wrote:
>
> > I've long been tired of seeing a failing job in Travis and then just
> seeing
> > a red "X" and a job number and then having to scroll through the log
> output
> > to figure out which particular build job failed. was it python? was it
> > .NET? was it just regular ol' mvn clean install?
> >
> > Well, I've managed to make some improvements and figured out how to stage
> > test runs into groups and then assign names to them - here's an example
> of
> > what it looks like now:
> >
> > https://travis-ci.org/apache/tinkerpop/builds/542862332
> >
> > Now, you see an "X", you immediately know what tanked. excellent
> >
>

Re: Travis Job Naming

Posted by Jorge Bay Gondra <jo...@gmail.com>.
Oh looks way cleaner! Thanks!

One thing we lost with this layout is the ability to run multiple test
groups in parallel, build time went from ~42mins
<https://travis-ci.org/apache/tinkerpop/builds/534940067> to 1h19m
<https://travis-ci.org/apache/tinkerpop/builds/543397816>.

The underlying reason is that TravisCI runs one stage after another
sequentially. We could group them into the same stage to get them to start
in parallel.

On Fri, Jun 7, 2019 at 9:44 PM Stephen Mallette <sp...@gmail.com>
wrote:

> I've long been tired of seeing a failing job in Travis and then just seeing
> a red "X" and a job number and then having to scroll through the log output
> to figure out which particular build job failed. was it python? was it
> .NET? was it just regular ol' mvn clean install?
>
> Well, I've managed to make some improvements and figured out how to stage
> test runs into groups and then assign names to them - here's an example of
> what it looks like now:
>
> https://travis-ci.org/apache/tinkerpop/builds/542862332
>
> Now, you see an "X", you immediately know what tanked. excellent
>