-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins 2.164.3
Kubernetes Plugin 1.15.4
I've been using Pipelines with EC2, ECS and now Kubernetes dynamic executors for some time.
I always noted an strange behavior but never found more information: When, by any reason, my agent dies, some Pipeline steps don't fail and keep running forever, unless I use timeout steps.
I just need to abort the job and it goes away.
Another strange thing is the executor stay present with the "offline" label, even the log displaying the failed connection. And it goes away with the job, when aborted.
- duplicates
-
JENKINS-49707 Auto retry for elastic agents after channel closure
-
- Resolved
-
-
JENKINS-56673 Better handling of ChannelClosedException in Declarative pipeline
-
- Resolved
-
- relates to
-
-
- Resolved
-