Re: [OMPI devel] Jenkins testing - what purpose are we striving to achieve?

my 0.02 US$ from an implementation point of view, the canonical way of using Jenkins with Github is 1) receive/poll a new PR 2) create a "check" and mark it pending 3) run a script 4) update the "check" status (OK/Failed) based on the exit status of the script. that being said, it is

Re: [OMPI devel] Jenkins testing - what purpose are we striving to achieve?

I would agree with all those points > On Jun 7, 2016, at 2:12 PM, Howard Pritchard wrote: > > HI Ralph, > > We briefly discussed this some today. I would like to avoid the mini-MTT > approach for PR checking. > At the same time, one can also see why it might be useful

Re: [OMPI devel] Jenkins testing - what purpose are we striving to achieve?

HI Ralph, We briefly discussed this some today. I would like to avoid the mini-MTT approach for PR checking. At the same time, one can also see why it might be useful from time to time to make changes to the script a given jenkins project runs on PRs. An idea we discussed was to have jenkins