Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71556

sh nodes in pipeline take a minute to execute

      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.

          [JENKINS-71556] sh nodes in pipeline take a minute to execute

          Chad added a comment -

          I checked the thread dump while a job is running and came across the following:

          	at DSL.sh(completed process (code 0) in /home/jenkins/workspace/test/pipeline tester@tmp/durable-bed04ebe on JNLP4-connect connection from ip-xx-xxx-xx-xxx.eu-west-1.compute.internal/xx.xxx.xx.xxx:44422; recurrence period: 300000ms; check task scheduled; cancelled? false done? false) 

          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.

          Chad added a comment - I checked the thread dump while a job is running and came across the following: at DSL.sh(completed process (code 0) in /home/jenkins/workspace/test/pipeline tester@tmp/durable-bed04ebe on JNLP4-connect connection from ip-xx-xxx-xx-xxx.eu-west-1.compute.internal/xx.xxx.xx.xxx:44422; recurrence period: 300000ms; check task scheduled; cancelled? false done? false ) 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.

            Unassigned Unassigned
            cestioco Chad
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: