Re: Travis Job Naming

2019-06-10 Thread Stephen Mallette
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 Gondr

Re: Travis Job Naming

2019-06-10 Thread Jorge Bay Gondra
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 to 1h19m . The underlying reason

Travis Job Naming

2019-06-07 Thread Stephen Mallette
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