Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Hudson shutdown wait from hell

On 02/08/2012 02:49 PM, David M Williams wrote:
> of Hudson .... seems several comments made or questions asked on this list
> with no response ... Hudson restarted, configuration changes all without
> comment. 
Just to close the loop on this one...  Sometime ago, we decided (via
this list) that webmasters wouldn't act on Hudson (or other infra)
issues based upon mail to cross-project, since this list is often used
to discuss issues which may or may not be confirmed yet.  In many cases
webmaster involvement isn't even required.  The real place to report
infra problems (and where we post updates) is in Bugzilla (and we
appreciate when folks post the bug number here).

Please consider that when something breaks, it's often reported on
multiple channels: bugs (sometimes a few) are open, emails are sent to
webmaster, emails are sent to myself, I get IMs, I get tweets, folks
send emails to Wayne and Mike, who in turn send more emails to me.

Posting updates in all these channels is time-consuming and
counter-productive (IMO).

> Is there some resistance to that? Everyone too busy to
> communicate? Is their a better channel? Hudson bug list? Do we need a
> "hudson-and-infrastructure" mailing list? Just asking.
Oh I hope not.  I think everyone has enough channels as it is  :)
> The queue is down to 26 now ... in the 10 minutes I took to write this
> note ... if that rate holds, it will be clear in 90 minutes or so? :/
I would think that's a normal (and reasonable) backlog.  If you need a
job pronto, Fastlane is there for you.  That's what we set it up for. 
It's currently idle.



> Thanks,
> From:	Miles Parker <milesparker@xxxxxxxxx>
> To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
> Date:	02/08/2012 02:22 PM
> Subject:	[cross-project-issues-dev] Hudson shutdown wait from hell
> Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx
> Hi all,
> I wanted to bring up a Hudson annoyance and see if people had ideas for
> improving this. What's happening now is that any time Hudson gets sent a
> shutdown, everyone is locked out until the last job in queue finishes.
> Which is a) Good news for the people with running builds, b) Bad news for
> everyone else. Observing that most of the time most of us are  in category
> b) I vote for making things work better for group b). Nothing against
> PTP :D, but they happen to be in group a) this time around and the last run
> took 22 hours. :O But there are lot's of long builds out there. This means
> that snapshots are delayed for everyone.
> So I'm wondering if it might be possible to have some kind of policy where
> builds are terminated with prejudice under shutdown. I'm not sure if a)
> this is even supportable OOTB in Hudson, and b) whether that would have the
> possibility of FUBAR'ing anyone project builds. As project builds should
> not be relying on previous state, I would say that the answer to b is
> probably no. I also imagine allowance should be made for key builds such as
> aggregator. IIRC in the past when in release panic mode we were triggering
> hard shutdowns from time to time.
> thoughts?
> Miles

Back to the top