Hi folks
I’m trying to get a handle on our use of Jenkins testing for PRs prior to
committing them. When we first discussed this, it was my impression that our
objective was to screen PRs to catch any errors caused by differences in
environment and to avoid regressions. However, it appears that
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 fol
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 from time to time
> to
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 p
