That pr seems to be for branch-2 and not master On June 10, 2020 5:17:19 PM GMT+02:00, David Mollitor <dam6...@gmail.com> wrote: >Zoltan, > >I just tried to close/re-open a PR and I don't believe it triggered a >new >CI run: > >https://github.com/apache/hive/pull/1076 > >Thanks. > >On Wed, Jun 10, 2020 at 10:59 AM David Mollitor <dam6...@gmail.com> >wrote: > >> Hey Zoltan, >> >> Can you please research a way to initiate it from the GitHub >interface? I >> have a strong feeling we're going to need such a capability >regularly. >> >> Thanks. >> >> On Wed, Jun 10, 2020 at 9:29 AM Zoltan Haindrich <k...@rxd.hu> wrote: >> >>> Hey >>> >>> you could: >>> * push new commits to the branch >>> - this will create a new merge with the current master >>> * login in to the jenkins instance: and launch a new build of that >PR >>> * close&re-open the pr: will re-emit the github event triggering the >>> testrun >>> * login in to the jenkins instance: and press retry button >>> >>> I don't know if the last method (retrigger button) will create a new >>> merge with the current master's HEAD or not - I suspect that it >doesn't. >>> >>> cheers, >>> Zoltan >>> >>> On 6/10/20 3:18 PM, David Mollitor wrote: >>> > Hey Zoltan, >>> > >>> > What is the process to trigger a new CI build on GitHub if a >previous >>> one >>> > failed on a flaky test. timeout, or something of that nature? >>> > >>> > Thanks. >>> > >>> >>
-- Zoltán Haindrich