Hundreds of person-hours are lost.

A few general hints what to do if the software you're using is so critical that a simple software crash has devastating effects:

  • Use the better tested LTS release line, rather than the weekly releases. Guess whose blood is on the 'bleeding edge'?
  • Pay someone (e.g. CloudBees offers paid Jenkins support) to provide support in case things go wrong.

This is a REALLY old bug, what gives?

This was reported as a task against the basically dead and unused Java.net plugin, so it should be no surprise this is getting ignored.

Change By: Daniel Beck (12/Oct/14 12:27 AM)
Issue Type: Task Bug
Labels: jenkins
Component/s: core
Component/s: javanet
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to