Hi Attila, Thanks for pointing this out. I have added "Delete workspace after build" as a post action to the jenkins job. This should hopefully resolve those issues in the future.
Thanks, Vivek Ratnavel On Fri, Jan 12, 2018 at 4:28 AM, Doroszlai, Attila <adorosz...@apache.org> wrote: > Hi Vivek, > > Sometimes the job seems to fail before checking out the change in the > pull request. > > https://builds.apache.org/job/Ambari-Github-PullRequest- > Builder/25/consoleText > https://builds.apache.org/job/Ambari-Github-PullRequest- > Builder/26/consoleText > https://builds.apache.org/job/Ambari-Github-PullRequest- > Builder/27/consoleText > > Here is a successful checkout for comparison: > > https://builds.apache.org/job/Ambari-Github-PullRequest- > Builder/21/consoleText > > Can you please check? Thanks. > > -Attila > > On Thu, Jan 11, 2018 at 7:58 PM, Vivek Ratnavel > <vivekratna...@apache.org> wrote: > > Hi Team, > > > > I am happy that the jenkins job works as expected. It gets triggered on > > every new pull request and performs the following tasks: > > > > Validate the merge > > Build Ambari > > Run unit tests > > > > The job will report failure if any one of these steps fail. Github UI > will > > show a pending check when the jenkins job is running. > > > > Please merge the PR only after the job is complete. > > > > Please let me know if you have any questions. > > > > Thanks, > > Vivek Ratnavel > > >
