Re: [OMPI devel] OMPI devel] Travis: one thing that might help

2017-02-09 Thread Josh Hursey
Looking at the IBM Jenkins setup we definitely have that option under "Build Triggers" -> "GitHub Pull Request Builder" -> "Trigger Setup" Then you can "Add" the "Cancel build on update" I'm not sure how well that would work for our setup (We would need the ability to drop a script in when it

Re: [OMPI devel] OMPI devel] Travis: one thing that might help

2017-02-09 Thread Jeff Squyres (jsquyres)
On Feb 9, 2017, at 4:38 AM, Gilles Gouaillardet wrote: > > Or maybe it used to be the case ... > see https://github.com/jenkinsci/ghprb-plugin/issues/379 for how to activate > this feature. LANL / Mellanox / IBM: can you guys check to see if you have this option

Re: [OMPI devel] OMPI devel] Travis: one thing that might help

2017-02-09 Thread Gilles Gouaillardet
Jeff, Or maybe it used to be the case ... see https://github.com/jenkinsci/ghprb-plugin/issues/379 for how to activate this feature. Back to travis, this feature is scheduled to happen in 2017Q1, See https://github.com/grosser/travis_dedup Cheers, Gilles Gilles Gouaillardet

Re: [OMPI devel] Travis: one thing that might help

2017-02-09 Thread Gilles Gouaillardet
Jeff, i made the test and it seems i got it wrong ... no travis build is cancelled when new commits are pushed into a PR :-( i could only note Mellanox Jenkins has a "stop" icon, so a build can be manually cancelled. LANL Jenkins nor Travis offer this option. Sorry for the confusion,

Re: [OMPI devel] Travis: one thing that might help

2017-02-08 Thread Jeff Squyres (jsquyres)
On Feb 8, 2017, at 10:15 AM, gil...@rist.or.jp wrote: > > iirc, i saw build being cancelled (i was monitoring the Jenkins console) > when new commits were pushed (or force pushed) to the current PR > > i will make a test tomorrow Oh, sweet. That would be good to know; thanks! > it is fair

Re: [OMPI devel] Travis: one thing that might help

2017-02-08 Thread gilles
Jeff, iirc, i saw build being cancelled (i was monitoring the Jenkins console) when new commits were pushed (or force pushed) to the current PR i will make a test tomorrow it is fair that using Travis for new PR is very likely more useful than for validating all builds Cheers, Gilles -

Re: [OMPI devel] Travis: one thing that might help

2017-02-08 Thread Jeff Squyres (jsquyres)
On Feb 8, 2017, at 9:34 AM, gil...@rist.or.jp wrote: > > i also noted that each time a PR is updated, a new Travis build is > started. > on the other hand, Jenkins is a bit smarter and does not build or cancel > "obsolete" PR. Are you sure? Here's how I thought Jenkins worked: - create a PR:

Re: [OMPI devel] Travis: one thing that might help

2017-02-08 Thread gilles
Jeff, i also noted that each time a PR is updated, a new Travis build is started. on the other hand, Jenkins is a bit smarter and does not build or cancel "obsolete" PR. i think most of us cannot manually direct Travis to cancel a given build. fwiw, building pushes is not useless. we recently

[OMPI devel] Travis: one thing that might help

2017-02-08 Thread Jeff Squyres (jsquyres)
I noticed the other evening that we are doing two things at Travis: 1. Building pull requests 2. Building pushes The 2nd one might well be contributing to our backlog (i.e., every time a PR is merged to the ompi repo, we Travis build again). I also confirmed with Travis that we're supposed to