I have a workflow job that cannot be killed, unless the java process
running Jenkins is killed. I think it is a bug. Here are the steps to
reproduce:
// Workflow job:
def flow
node() {
git 'file:///home/martin/git/workflow-job-definition.git'
flow = load 'flow.groovy'
}
def m = flow.createMyClass("Joe")
assert m.getName() == "Joe"
// Content of flow.groovy
class MyClass {
String name
MyClass(String name) {
this.name = name
}
String getName() {
return "the name is: "+name
}
}
MyClass createMyClass(String name) {
return new MyClass(name)
}
return this
Once the job has started, it consumes more and more memory. To kill it, I
have to use kill -11 on the java process id (control-c is not enough). When
Jenkins restarts, it resumes the hanging job, but this time I can kill it
from the UI. I use Jenkins 1.638, and Workflow 1.11, on linux mint
I tried looking for similar issues, but I cannot find if this has already
been reported.
Martin
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/ab0c0a64-977a-4f79-9199-33893abec670%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
