Use your best judgement. Travis right now provides multi-JDK, multi-platform coverage not available in Jenkins. If the change is not sensitive to that, it is probably reasonable to proceed.
On Wed, Mar 1, 2017 at 9:01 AM, Amit Sela <[email protected]> wrote: > +1 > Can we merge PRs without waiting for Travis as long as it's not working ? > > On Wed, Mar 1, 2017 at 6:52 PM Davor Bonaci <[email protected]> wrote: > > > It cannot be done at this time. > > > > We should really move all Travis coverage into Jenkins and completely > > deprecate Travis. I know Jason is looking into that ;-) > > > > On Wed, Mar 1, 2017 at 3:51 AM, Amit Sela <[email protected]> wrote: > > > > > Hi all, > > > > > > Recently I've encountered PRs where everything was green in Jenkins but > > > Travis was stuck and didn't execute. > > > I couldn't (as the committer/reviewer) to do the same "retest this > > please" > > > magic we apply to Jenkins, and I don't know of the possibility to do > this > > > in Travis. > > > I know that on "my" Travis I can "Restart Build" but I'm not sure > > > contributors can do so on their, and I couldn't (on someone else's PR). > > > > > > Anyone knows how we can make this easier ? > > > > > > Appreciate the help. > > > > > > Amit > > > > > >
