Thank you Srikanth, that helps explain it. I will help Ying (or other team members) if they have to re-run builds.
Balu On 2/19/16, 8:32 AM, "Srikanth Sundarrajan" <[email protected]> wrote: >I believe build setup is configured on apache infra resources and are >secured with apache login. This is by design and something individual >projects can't change. For more details on build infrastructure, please >see http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson > >Regards >Srikanth Sundarrajan > >> Subject: Re: github pull request model - Pre commit build timeout >> From: [email protected] >> To: [email protected] >> Date: Thu, 18 Feb 2016 19:41:57 +0000 >> >> +1 >> >> If all the users/contributors cannot be provided Jenkins access then its >> committers responsibility to monitor failed pull request builds and >>rerun >> it for intermittent build failures. Is this the workflow we want to >>follow? >> >> Thanks! >> >> On 2/18/16, 11:32 AM, "Balu Vellanki Bala" <[email protected]> >> wrote: >> >> >Hi Srikanth, >> > >> >I was unable to login using github account "bvellanki". Ying Zheng >> >(yzheng-hortonworks) could not do so either. I could login and >>trigger a >> >re-run using committer account (balu@). Is this by design? >> > >> >If yes, I believe we should allow all contributors to be able to re-run >> >failed builds. >> > >> >Thanks >> >Balu >> > >> >On 2/17/16, 6:53 PM, "Srikanth Sundarrajan" <[email protected]> >>wrote: >> > >> >>Hi Sowmya, >> >> You should have permissions to re-run I believe. Were you logged >>into >> >>the build system using your apache-id. I often missed this step and >> >>wondered why dont see an option to run a job. If you had indeed >>logged in >> >>and yet dont have permissions to run the job, do report back. >> >> >> >>Regards >> >>Srikanth Sundarrajan >> >> >> >>> Subject: Re: github pull request model - Pre commit build timeout >> >>> From: [email protected] >> >>> To: [email protected] >> >>> Date: Thu, 18 Feb 2016 01:25:40 +0000 >> >>> >> >>> Raghav - I didn¹t have the permissions to rebuild the failed job. >> >>> I agree rebuilding will suffice but will all the users/contributors >> >>>have >> >>> Jenkins access? >> >>> >> >>> Thanks! >> >>> >> >>> On 2/17/16, 5:06 PM, "Raghav Kumar Gautam" <[email protected]> >> >>>wrote: >> >>> >> >>> >Hi Sowmya, >> >>> > >> >>> >Just rerunning the job suffices. I have started it for your pull >> >>>request >> >>> >and the new job is making progress. >> >>> > >> >>> >Thanks, >> >>> >Raghav. >> >>> > >> >>> > >> >>> >Raghav Kumar Gautam >> >>> >http://www.linkedin.com/in/raghavg >> >>> > >> >>> >On Wed, Feb 17, 2016 at 1:07 PM, Sowmya Ramesh >> >>><[email protected]> >> >>> >wrote: >> >>> > >> >>> >> Hi All, >> >>> >> >> >>> >> For one of my pull request, build failed and in the console build >> >>>log I >> >>> >> see below issue where build timed out and was aborted. >> >>> >> >> >>> >> ""Build timed out (after 90 minutes). Marking the build as >>failed. >> >>> >> Build was aborted" >> >>> >> >> >>> >> I don't think user/contributor will have the permissions to >>rebuild. >> >>> >> Any ideas on how to handle these kind of build failures? >> >>> >> >> >>> >> Thanks! >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >> > >> >
