Does this require a Seed Job rerun? I'm seeing Python postcommits breaking as well
On Wed, May 9, 2018 at 10:49 AM Alan Myrvold <amyrv...@google.com> wrote: > I saw ~1-2 hour latency for the trigger happening yesterday. Not sure what > would cause it to stop or be slow. > > On Wed, May 9, 2018 at 10:45 AM Lukasz Cwik <lc...@google.com> wrote: > >> It seems as though precommits are no longer triggering and trigger >> requests like 'Run Java PreCommit' are no longer honored. >> >> On Wed, May 9, 2018 at 10:22 AM Andrew Pilloud <apill...@google.com> >> wrote: >> >>> I broke all the post commits with this. Sorry! It has been reverted. I'm >>> going to follow up with Apache Infra about getting the right credentials >>> configured on the Jenkins plugin. >>> >>> Andrew >>> >>> On Tue, May 8, 2018 at 1:38 PM Andrew Pilloud <apill...@google.com> >>> wrote: >>> >>>> Yep, mess with the groovy scripts appears to be the answer. We use >>>> different jenkins libraries to handle PRs vs pushes to master but I think I >>>> finally figured it out. Change is here: >>>> https://github.com/apache/beam/pull/5305 >>>> >>>> Andrew >>>> >>>> On Mon, May 7, 2018 at 12:40 PM Kenneth Knowles <k...@google.com> wrote: >>>> >>>>> I think you want to mess with the groovy scripts in .test-infra/jenkins >>>>> >>>>> Kenn >>>>> >>>>> On Mon, May 7, 2018 at 11:12 AM Andrew Pilloud <apill...@google.com> >>>>> wrote: >>>>> >>>>>> The Github branches page shows the status of the latest commit on >>>>>> each branch and provides a set of links to the jobs run on that commit. >>>>>> But >>>>>> it doesn't appear Jenkins is publishing status from post commit jobs. >>>>>> This >>>>>> seems like a simple oversight that should be easy to fix. Could someone >>>>>> point me in the right direction to fix this? >>>>>> >>>>>> Andrew >>>>>> >>>>> -- Got feedback? go/pabloem-feedback
