Hi, This week the machine running Hive builds at http://bigtop01.cloudera.org:8080/view/Hive/? ran out of space, so new jobs like Precommit tests stopped. Its still not resolved there, there was another email today on Bigtop list, but there's very few people with root access to that host, and they still haven't responded.
I chatted with Brock, he has also seen various issues with Bigtop jenkins in the past, so I am thinking to move the Jenkins jobs to the PTest master itself, where some PMC already have access and can admin if needed. Currently I am hosting the pre-commit Jenkins job on my own EC2 instance as stop-gap. Other advantages of hosting our own Jenkins: 1. No need to wait for other Bigtop jobs to run. 2. Bigtop is using a version of Jenkins that doesnt show parameters like JIRA number for queued jobs, so impossible to tell whether a patch got picked up and where it is in queue. 3. Eliminate network hop from Bigtop box to our PTest master. The disadvantage is: 1. We don't have much experience doing Jenkins admin, but it doesn't look too bad. Mostly, restart if there's issue and clean up if out of space. I wonder what people think, and if there's any objections to this? If not, I'll try setting up this weekend. Then, there is some follow-up work, like changing the Jenkins url's displayed in the test report. Thanks! Szehon
