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

          Created a PR with a proposed fix:
          https://github.com/jenkinsci/build-pipeline-plugin/pull/65

          Please test it.

          Patrik Boström added a comment - Created a PR with a proposed fix: https://github.com/jenkinsci/build-pipeline-plugin/pull/65 Please test it.

          Code changed in jenkins
          User: Patrik Boström
          Path:
          src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java
          src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuild.java
          src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly
          src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuildTest.java
          http://jenkins-ci.org/commit/build-pipeline-plugin/7a52b7429065821552f89946784853ee70a6d0dc
          Log:
          JENKINS-20499 If a job has two upstream dependencies and it has been triggered by anything except the manual trigger it will always take the first upstream job as the upstream dependency even if it is incorrect. Added check to not add a null Cause if upstream build is null.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Patrik Boström Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuild.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuildTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/7a52b7429065821552f89946784853ee70a6d0dc Log: JENKINS-20499 If a job has two upstream dependencies and it has been triggered by anything except the manual trigger it will always take the first upstream job as the upstream dependency even if it is incorrect. Added check to not add a null Cause if upstream build is null.

          Code changed in jenkins
          User: Geoff Bullen
          Path:
          src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java
          src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuild.java
          src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly
          src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuildTest.java
          http://jenkins-ci.org/commit/build-pipeline-plugin/f4a8d984a2b169219d6eb7187aaef49af9d9fc4c
          Log:
          Merge pull request #65 from patbos/JENKINS-20499

          merged JENKINS-20499

          Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/fe118c684376...f4a8d984a2b1

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Geoff Bullen Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuild.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuildTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/f4a8d984a2b169219d6eb7187aaef49af9d9fc4c Log: Merge pull request #65 from patbos/ JENKINS-20499 merged JENKINS-20499 Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/fe118c684376...f4a8d984a2b1

          Libero Scarcelli added a comment - - edited

          This one should be fixed now... but you need to update Core and pipeline plugin: I can see most of you are using a very old version of Jenkins and Pipeline plugin. I am pretty sure an update would fix this. I would recommend you to run at least Jenkins version 1.580.3 + Build Pipeline Plugin 1.4.5

          Libero Scarcelli added a comment - - edited This one should be fixed now... but you need to update Core and pipeline plugin: I can see most of you are using a very old version of Jenkins and Pipeline plugin. I am pretty sure an update would fix this. I would recommend you to run at least Jenkins version 1.580.3 + Build Pipeline Plugin 1.4.5

          Toralf B added a comment -

          Hello,
          I'm using Jenkins version 1.596.1 + Build Pipeline Plugin 1.4.5, and still got the problem with the retry of a broken build - still the problem "java.lang.IllegalStateException: No upstream trigger found for this projectTest12 ..."
          Since the merge of "pull request #65 from patbos/JENKINS-20499" is very new and the pipeline plugin version is built on November, 26th, I have the question if there is a workaround for this error?
          When there might be a new version of the PipelinePlugin including the fix?

          Toralf B added a comment - Hello, I'm using Jenkins version 1.596.1 + Build Pipeline Plugin 1.4.5, and still got the problem with the retry of a broken build - still the problem "java.lang.IllegalStateException: No upstream trigger found for this projectTest12 ..." Since the merge of "pull request #65 from patbos/ JENKINS-20499 " is very new and the pipeline plugin version is built on November, 26th, I have the question if there is a workaround for this error? When there might be a new version of the PipelinePlugin including the fix?

          Hello Toralf... what happens if you disable the option "Prevent Cross Site Request Forgery exploits"?

          Libero Scarcelli added a comment - Hello Toralf... what happens if you disable the option "Prevent Cross Site Request Forgery exploits"?

          siemfabio added a comment -

          siemfabio added a comment - I found the perfect combination! Jenkins-CORE 1.565 http://mirrors.jenkins-ci.org/war/1.565/jenkins.war build-pipeline-plugin 1.4.3 http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/plugins/build-pipeline-plugin/1.4.3/build-pipeline-plugin-1.4.3.hpi

          Toralf B added a comment - - edited

          Hello Libero,
          the option is disabled by default. So this option doesn't help, sadly.

          Toralf B added a comment - - edited Hello Libero, the option is disabled by default. So this option doesn't help, sadly.

          Should be fixed with 1.4.6 version

          Kanstantsin Shautsou added a comment - Should be fixed with 1.4.6 version

          Removing lts-candidate label as PR 1248 is a part of 1.596 baseline.

          Oliver Gondža added a comment - Removing lts-candidate label as PR 1248 is a part of 1.596 baseline.

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

              Created:
              Updated:
              Resolved: