So I managed to fix the Apache Jenkins build environment. For future reference, here are my notes:
- In the Apache Jenkins environment for Incubator projects, only a few members of the PPMC have editing ability. I only know that Radar and I have access. It is possible others may also have access as well. - The Apache Jenkins build slave "ubuntu-4" was consistently encountering a problem during cloning process because files were left over from a previous build (not sure which one) that left files owned by "root". - To gain access to the build environment, I modified the project by changing SCM to "none" and updated the script to load the docker container and then remove the previous directories. I was able to rebuild the job as it never actually performed a git operation. I then restored the project to it's previous configuration. - This resolved the git cloning issue. However, the build job still failed as the docker image was missing components required for building. - I wasn't able to rebuild the job as I continued testing because the PR information is only available when the job is automatically triggered from an update to a PR. I created a test PR where I pushed noop changes to be able to trigger PR builds in the Apache Jenkins service. - I modified the container to use "rlei/mydocker:centos7-build" instead of "rlei/mydocker:latest". With this change, the build finally succeeded. Thanks to Hubert for pointing out the issue. Thanks to Radar for being an excellent sounding board and providing an updated container to use for the time being. Cheers, -=e On Sun, Feb 26, 2017 at 11:55 PM, Radar Da lei <[email protected]> wrote: > Recently jenkins failures seems like environment issue of Apache jenkins > build host. We might file a ticket to solve it. > > I checked previously build which reported as success, seems it will > actually failed to do "./configure", the reason is the docker image used to > build HAWQ is out of date. This means jenkins actually not working for a > long time. > > We should update the docker image first then fix the PR Jenkins jobs. > Before that, I feel we are ok to ignore it since it's not working at all. > Thanks. > > Regards, > Radar > > On Mon, Feb 27, 2017 at 3:31 PM, Ed Espino <[email protected]> wrote: > > > FYI: In order to debug this and as it is impacting all PR builds in the > > Apache Jenkins environment, I will be manually triggering builds to try > and > > understand and resolve this issue. I may also be aborting current jobs so > > please do not be alarmed if your PR's Apache Jenkins check aborts. > > > > -=e > > > > On Sun, Feb 26, 2017 at 10:56 PM, Ed Espino <[email protected]> wrote: > > > > > Hubert, > > > > > > The Pull Request (PR) jobs take place in the Apache Jenkins service > > > HAWQ-build-pullrequest > > > <https://builds.apache.org/job/HAWQ-build-pullrequest/> job. This was > in > > > place prior to me actively joining the Apache HAWQ dev community. I > have > > > just noticed the jobs for multiple PRs have been failing for the same > > > reason. I will take a look to see if I can identify what the core issue > > is. > > > > > > BTW: I have CC'd the dev list for wider visibility. Maybe someone on > the > > > list can also provide some insight on this issue. > > > > > > -=e > > > > > > > > > On Sun, Feb 26, 2017 at 9:50 PM, Hubert Zhang <[email protected]> > wrote: > > > > > >> Hi Ed, > > >> > > >> Jenkins (build of PR1146) cannot clean up environment with the > following > > >> error messages: > > >> > > >> Cloning the remote Git repository > > >> > > >> Cloning repository git://github.com/apache/incubator-hawq.git > > >> > > >> ERROR: Failed to clean the workspace > > >> java.io.IOException: Unable to delete '/home/jenkins/jenkins-slave/ > > workspace/HAWQ-build-pullrequest'. Tried 3 times (of a maximum of 3) > > waiting 0.1 sec between attempts. > > >> > > >> > > >> > > >> I think it's an environment issue and PR1146 is the blocker of HDB > > >> pipeline, so we will +1 firstly to push the code and make HDB pipeline > > >> green. > > >> > > >> Could you also show some hints on how to fix Jenkins env problem, and > we > > >> can fix it by ourselves next time. > > >> > > >> -- > > >> Thanks > > >> > > >> Hubert Zhang > > >> > > > > > > > > > > > > -- > > > *Ed Espino* > > > *[email protected] <[email protected]>* > > > > > > > > > > > -- > > *Ed Espino* > > *[email protected] <[email protected]>* > > > -- *Ed Espino* *[email protected] <[email protected]>*
