-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.401.1
I have a fresh Jenkins instance running on EC2 via ECS. "sh" nodes in the pipeline, no matter how simple, take a minute to execute (see screenshots). I should not that if I run the job on the master node, this behavior does not occur.
What could be the culprit here? The worker image itself is just a slightly-modified jenkins/inbound-agent:jdk11 with the workspace directory mapped to an EBS volume. This looks to me more like a consistent overhead of 1 minute for "sh" commands.
I checked the thread dump while a job is running and came across the following:
I am confused here. Why does it say "completed process (code 0)" but at the same time "done? false"? It seems to me this might be related to my problem.