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

unable to retry job execution for failed job in build-pipeline

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • build-pipeline-plugin
    • None
    • OS Linux Red Hat 6.3, Jenkins core 1.529, build pipeline plugin 1.4.2, parametrized trigger plugin 2.21

      a new run with "retry" link on failed job get stuck without any output in console. log exception:

      Nov 9, 2013 1:04:34 AM hudson.model.Executor run
      SEVERE: Executor threw an exception
      java.lang.NullPointerException
      at hudson.model.CauseAction.onAttached(CauseAction.java:120)
      at hudson.model.Run.addAction(Run.java:349)
      at hudson.model.Executor.run(Executor.java:238)

      the run cannot be aborted or cancelled. the only way to stop it is restarting Jenkins.

          [JENKINS-20499] unable to retry job execution for failed job in build-pipeline

          siemfabio created issue -

          siemfabio added a comment -

          the run status page shows this exception:

          javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.529.jar!/hudson/model/CauseAction/summary.jelly:30:65: <st:include> No page found 'description.jelly' for class hudson.model.CauseAction
          at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
          at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)

          find full stacktrace attached

          siemfabio added a comment - the run status page shows this exception: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar: file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.529.jar!/hudson/model/CauseAction/summary.jelly:30:65: <st:include> No page found 'description.jelly' for class hudson.model.CauseAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) find full stacktrace attached
          siemfabio made changes -
          Attachment New: stacktrace.txt [ 24649 ]
          siemfabio made changes -
          Description Original:  a new run with "retry" link on failed the job get stuck without any output in console. log exception:

          Nov 9, 2013 1:04:34 AM hudson.model.Executor run
          SEVERE: Executor threw an exception
          java.lang.NullPointerException
                  at hudson.model.CauseAction.onAttached(CauseAction.java:120)
                  at hudson.model.Run.addAction(Run.java:349)
                  at hudson.model.Executor.run(Executor.java:238)

          the run cannot be aborted or cancelled. the only way to stop it is restarting Jenkins.
          New:  a new run with "retry" link on failed job get stuck without any output in console. log exception:

          Nov 9, 2013 1:04:34 AM hudson.model.Executor run
          SEVERE: Executor threw an exception
          java.lang.NullPointerException
                  at hudson.model.CauseAction.onAttached(CauseAction.java:120)
                  at hudson.model.Run.addAction(Run.java:349)
                  at hudson.model.Executor.run(Executor.java:238)

          the run cannot be aborted or cancelled. the only way to stop it is restarting Jenkins.
          Environment Original: Linux Red Hat 6.3 New: OS Linux Red Hat 6.3, Jenkins core 1.529, build pipeline plugin 1.4.2, parametrized trigger plugin 2.21

          This repos on the following environment:

          Windows Server 2008 R2
          Jenkins core 1.537
          Build Pipeline plugin 1.4.1
          Parametrized Trigger plugin 2.18

          It occurs when a build is forced (Click "Build with Parameters", click "Build") after a failed build.

          Kyle Parker-Robinson added a comment - This repos on the following environment: Windows Server 2008 R2 Jenkins core 1.537 Build Pipeline plugin 1.4.1 Parametrized Trigger plugin 2.18 It occurs when a build is forced (Click "Build with Parameters", click "Build") after a failed build.

          I am getting exactly the same problem and stacktrace (version 1.4.1 with Jenkins LTS 1.509.4) After triggering the same downstream project from two different upstream projects

          Steps to reproduce:
          1. Create a downstream project D
          2. Create Projects A and B. As post-build action select "Build Other Projects (manual step)" and select for both: Project D. Add some predefined parameters: (e.g MY_VAR = VALUE)
          3. Create two Build Pipeline Views: One for Project A and one for Project B
          4. Trigger downstream project D from Project A using its corresponding Build Pipeline View
          5. Trigger downstream project D from Project B using its corresponding Build Pipeline View
          6. Repeat 4 and 5 a couple of times. D runs broken and cannot be aborted

          David Fuenmayor added a comment - I am getting exactly the same problem and stacktrace (version 1.4.1 with Jenkins LTS 1.509.4) After triggering the same downstream project from two different upstream projects Steps to reproduce: 1. Create a downstream project D 2. Create Projects A and B. As post-build action select "Build Other Projects (manual step)" and select for both: Project D. Add some predefined parameters: (e.g MY_VAR = VALUE) 3. Create two Build Pipeline Views: One for Project A and one for Project B 4. Trigger downstream project D from Project A using its corresponding Build Pipeline View 5. Trigger downstream project D from Project B using its corresponding Build Pipeline View 6. Repeat 4 and 5 a couple of times. D runs broken and cannot be aborted

          João Vale added a comment -

          Same problem here, with the same NullPointerException.

          CentOS 6.4
          Jenkins 1.536
          Build Pipeline 1.4.2

          João Vale added a comment - Same problem here, with the same NullPointerException. CentOS 6.4 Jenkins 1.536 Build Pipeline 1.4.2

          Same problem but without parameterized-trigger involved
          CentOS 6.4
          Jenkins LTS 1.532.1
          Build Pipeline 1.4.2

          #1 A (success) -> B (success)
          #2 A (failure) -> B (skipped)
          #3 A (stuck)

          Though i was not able to reproduce it myself yet

          Dzmitry Horbach added a comment - Same problem but without parameterized-trigger involved CentOS 6.4 Jenkins LTS 1.532.1 Build Pipeline 1.4.2 #1 A (success) -> B (success) #2 A (failure) -> B (skipped) #3 A (stuck) Though i was not able to reproduce it myself yet

          Same problem here

          Jenkins ver. 1.532.1
          Parameterized Trigger plugin 2.22
          Build Pipeline Plugin 1.4.2

          Daniel Gonzalez added a comment - Same problem here Jenkins ver. 1.532.1 Parameterized Trigger plugin 2.22 Build Pipeline Plugin 1.4.2

          Zachary Young added a comment -

          Same here

          Jenkins 1.550
          Parameterized Trigger plugin 2.22
          Build Pipeline Plugin 1.4.2

          Zachary Young added a comment - Same here Jenkins 1.550 Parameterized Trigger plugin 2.22 Build Pipeline Plugin 1.4.2

            huybrechts huybrechts
            siemfabio siemfabio
            Votes:
            22 Vote for this issue
            Watchers:
            34 Start watching this issue

              Created:
              Updated:
              Resolved: