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

Execute shell is terminated randomly

    XMLWordPrintable

Details

    Description

      After upgrading to 1.600 I am getting build errors on all jobs that has a "Execute shell" build step

      I tried downgrading to 1.599 and everything works there.
      I tried with both sh and bash
      It looks like the shell commands are terminated randomly in the middle of the run

      I tested with a very simple script like :

      sleep 59
      echo "sleep done"

      and got :

      Started by timer
      [EnvInject] - Loading node environment variables.
      Building remotely on cis01.coolsmsc.dk (swarm) in workspace /home/jenkinsslave/workspace/cron - test - test-no-php
      [cron - test - test-no-php] $ /bin/bash -xe /tmp/hudson4904788725429931154.sh
      + sleep 59
      /tmp/hudson4904788725429931154.sh: line 2: 19627 Terminated sleep 59
      Build step 'Execute shell' marked build as failure
      Finished: FAILURE

      Attachments

        Issue Links

          Activity

            The release notes for 1.601 (see http://jenkins-ci.org/changelog) do not mention this ticket. Was the fix released nevertheless?

            phraktle Viktor Szathmary added a comment - The release notes for 1.601 (see http://jenkins-ci.org/changelog ) do not mention this ticket. Was the fix released nevertheless?
            jglick Jesse Glick added a comment -

            changelog.html probably got messed up by rc branch madness.

            jglick Jesse Glick added a comment - changelog.html probably got messed up by rc branch madness.
            danielbeck Daniel Beck added a comment -

            This was logged as JENKINS-21788, a duplicate of this issue.

            danielbeck Daniel Beck added a comment - This was logged as JENKINS-21788 , a duplicate of this issue.
            allancarter Allan Carter added a comment -

            I'm still seeing a similar issue in release 1.637. If I run multiple executors then jenkins randomly sends SIGTERM to all the jobs processes. Am I seeing something new or did this not get integrated?

            allancarter Allan Carter added a comment - I'm still seeing a similar issue in release 1.637. If I run multiple executors then jenkins randomly sends SIGTERM to all the jobs processes. Am I seeing something new or did this not get integrated?
            danielbeck Daniel Beck added a comment -

            allancarter Probably a different issue. Please file a new bug.

            danielbeck Daniel Beck added a comment - allancarter Probably a different issue. Please file a new bug.

            People

              johno Johno Crawford
              hmn Henrik Nicolaisen
              Votes:
              6 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: