Jenkins job termination needs serious engineering help

833 views
Skip to first unread message

Rinaldo DiGiorgio

unread,
Nov 16, 2016, 8:57:26 AM11/16/16
to Jenkins Users
It has been over a year of dealing with Job termination in jenkins requiring one to find an html link in a console output file that is scrolling at a very fast rate. It is mind boggling that an action like that is not sent to some queue in a reasonable interface for someone to act on.  Let's not even discuss it is using a javascript dialog which give you no additional information.


Jason Pyeron

unread,
Nov 17, 2016, 6:43:44 AM11/17/16
to jenkins...@googlegroups.com
> -----Original Message-----
> From: Rinaldo DiGiorgio
> Sent: Wednesday, November 16, 2016 08:57
>
> It has been over a year of dealing with Job termination in
> jenkins requiring one to find an html link in a console
> output file that is scrolling at a very fast rate.

Please explain, not sure I am following the issue.

> It is mind
> boggling that an action like that is not sent to some queue
> in a reasonable interface for someone to act on. Let's not
> even discuss it is using a javascript dialog which give you
> no additional information.

Not sure I understand this email, what is the problem or desired outcome?

Daniel Beck

unread,
Nov 17, 2016, 7:30:12 AM11/17/16
to jenkins...@googlegroups.com

> On 17.11.2016, at 12:43, Jason Pyeron <jpy...@pdinc.us> wrote:
>
> Please explain, not sure I am following the issue.

He's complaining about https://issues.jenkins-ci.org/browse/JENKINS-33721

Rinaldo DiGiorgio

unread,
Jan 19, 2017, 10:32:41 AM1/19/17
to Jenkins Users, m...@beckweb.net
I am not complaining, I appreciate Open Source and all the work being done by the Jenkins community. if I understood the class structure more I would into it.  A slightly related issue has to do with the following.  We used the nice new timeout step in pipeline and it tirggered as expected, we had issues with it because it geneerated an exception we had not accounted for. When the timeout occurs the job doesn't complete processing.  Is there some additional action I can take to cause the job to timeout. We run 100s of jobs and want to avoid logging in to resolve the issue. I had to click abort and then find the link the console log.

04:02:18.568 Body did not finish within grace period; terminating with extreme prejudice
[Pipeline] // parallel
[Pipeline] }
[Pipeline] [tier1-solaris-sparcv9] }
[Pipeline] // timeout
[Pipeline] echo
04:02:18.606 SEVERE: Timeout org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
[Pipeline] echo
04:02:18.608 ------End jdk9-dev workflow script-----------
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] [tier1-solaris-sparcv9] }
Aborted by anonymous
Click here to forcibly terminate running steps
Terminating dir

Reply all
Reply to author
Forward
0 new messages