I noticed that the Hive job mentioned below has been hogging build time on Jenkins, which means our jobs have to wait many hours to run. I'm a firm believer in using CI servers to give timely feedback, so this situation irks me.
I haven't yet had a response from any Hive developers. I'm considering asking [email protected] to disable this job if it doesn't get fixed soon, but I'm not sure of the etiquette. Any fellow Qpid devs got a view on what the appropriate course of action is? Phil ---------- Forwarded message ---------- From: "Phil Harvey" <[email protected]> Date: Feb 23, 2013 11:06 PM Subject: Apache Jenkins job repeatedly falling To: <[email protected]> Cc: Hi, > > Whilst looking at another Apache project I noticed that the Jenkins job > Hive-trunk-hadoop2 [1] has been failing for several weeks, sometimes taking > 13 hours to do so. This doesn't seem to be a good use of the very congested > Jenkins servers. Presumably the Hive developers are getting little value > from a build that always fails. > > Is this being looked at? > > If there are no plans to fix this job soon then maybe it should be > disabled. > > Thanks, > Phil > > [1] https://builds.apache.org/job/Hive-trunk-hadoop2/ >
