• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • build-pipeline-plugin
    • None
    • Jenkins: 1.519
      Build Pipeline Plugini: 1.3.4.1

      Build Pipeline Plugin throw the next exception when I click in the run button:

      WARNING: Untrapped Error in Servlet
      org.kohsuke.stapler.ForwardToView
      	at org.kohsuke.stapler.HttpResponses.forwardToView(HttpResponses.java:213)
      	at hudson.model.BuildAuthorizationToken.checkPermission(BuildAuthorizationToken.java:87)
      	at hudson.model.AbstractProject.doBuild(AbstractProject.java:1791)
      	at au.com.centrumsystems.hudson.plugin.buildpipeline.DownstreamProjectGridBuilder$1.generateResponse(DownstreamProjectGridBuilder.java:172)
      	at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:105)
      	at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:63)
      	at org.kohsuke.stapler.Function.renderResponse(Function.java:103)
      	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:92)
      

      Thanks in advance,

          [JENKINS-18490] Run button not work

          louis gueye added a comment -

          Same problem here: clicking /view/<pipeline_name>/gridBuilder/build has no effect. It doesn't start a new build.
          Also, retrying a failing step in the pipeline doesn't create a new build.

          louis gueye added a comment - Same problem here: clicking /view/<pipeline_name>/gridBuilder/build has no effect. It doesn't start a new build. Also, retrying a failing step in the pipeline doesn't create a new build.

          Ben Morgan added a comment -

          Same problem here on 1.527 of Jenkins and 1.3.5 of the pipeline plugin. I see the problem where the initial job is parameterised but it works fine where the initial job is not parameterised.

          Ben Morgan added a comment - Same problem here on 1.527 of Jenkins and 1.3.5 of the pipeline plugin. I see the problem where the initial job is parameterised but it works fine where the initial job is not parameterised.

          The original stack trace in the issue description is fixed in fafe5fb2da87c0ac2a33a3fbcc10267031740c72 in stapler 1.211, which got integrated into Jenkins 1.520.

          Kohsuke Kawaguchi added a comment - The original stack trace in the issue description is fixed in fafe5fb2da87c0ac2a33a3fbcc10267031740c72 in stapler 1.211, which got integrated into Jenkins 1.520.

          Mir Mehdi added a comment -

          New version of plugin has been released. Build Pipeline 1.4 (Required core 1.521).
          Run button works and the retry trigger for failed jobs is taking the parameters. Only feature missing is, the trigger is limited to new/failed jobs. You cannot re-run a successful jobs again.

          Mir Mehdi added a comment - New version of plugin has been released. Build Pipeline 1.4 (Required core 1.521). Run button works and the retry trigger for failed jobs is taking the parameters. Only feature missing is, the trigger is limited to new/failed jobs. You cannot re-run a successful jobs again.

          Jesse Glick added a comment -

          Jesse Glick added a comment - https://github.com/jenkinsci/build-pipeline-plugin/commit/ad7093f2596eafed61d59d0a21c82b8f8995d587 was the fix; not sure why the JIRA notifier failed to link it.

          Jesse Glick added a comment -

          @sajjadmehdi:

          the trigger is limited to new/failed jobs. You cannot re-run a successful jobs again.

          That sounds like an RFE, unrelated to this bug report.

          Jesse Glick added a comment - @sajjadmehdi: the trigger is limited to new/failed jobs. You cannot re-run a successful jobs again. That sounds like an RFE, unrelated to this bug report.

          Log:
          сен 16, 2013 6:59:35 AM WARNING winstone.Logger logInternal
          Content-length said 9, actual length was 0
          сен 16, 2013 6:59:36 AM WARNING winstone.Logger logInternal
          Content-length said 9, actual length was 0
          сен 16, 2013 7:05:58 AM WARNING winstone.Logger logInternal
          Content-length said 9, actual length was 0
          сен 16, 2013 7:06:02 AM WARNING winstone.Logger logInternal
          Content-length said 9, actual length was 0
          сен 16, 2013 7:10:17 AM WARNING winstone.Logger logInternal
          Content-length said 9, actual length was 0

          When I click on "Run" nothing happens

          Jenkins ver. 1.530
          Plugin Pipeline ver. 1.4

          Andrey Yakovlev added a comment - Log: сен 16, 2013 6:59:35 AM WARNING winstone.Logger logInternal Content-length said 9, actual length was 0 сен 16, 2013 6:59:36 AM WARNING winstone.Logger logInternal Content-length said 9, actual length was 0 сен 16, 2013 7:05:58 AM WARNING winstone.Logger logInternal Content-length said 9, actual length was 0 сен 16, 2013 7:06:02 AM WARNING winstone.Logger logInternal Content-length said 9, actual length was 0 сен 16, 2013 7:10:17 AM WARNING winstone.Logger logInternal Content-length said 9, actual length was 0 When I click on "Run" nothing happens Jenkins ver. 1.530 Plugin Pipeline ver. 1.4

          Jesse Glick added a comment -

          @suffrage: tested 1.4 on 1.530 and the Run button worked fine. There was a confirmed and analyzed bug here which was fixed. If under some circumstances the Run button is not working for you, it is most likely some other bug. If you figure out how to reproduce it (and your JavaScript console / network debugger will probably need to come into play), please file a separate bug report.

          Jesse Glick added a comment - @suffrage: tested 1.4 on 1.530 and the Run button worked fine. There was a confirmed and analyzed bug here which was fixed. If under some circumstances the Run button is not working for you, it is most likely some other bug. If you figure out how to reproduce it (and your JavaScript console / network debugger will probably need to come into play), please file a separate bug report.

          http://www.youtube.com/watch?v=NeE43s-15qE&feature=youtu.be
          Video proof

          Log:
          Sep 30, 2013 2:19:23 PM winstone.Logger logInternal
          WARNING: Content-length said 9, actual length was 0
          Sep 30, 2013 2:19:25 PM winstone.Logger logInternal
          WARNING: Content-length said 9, actual length was 0
          Sep 30, 2013 2:19:27 PM winstone.Logger logInternal
          WARNING: Content-length said 9, actual length was 0

          Andrey Yakovlev added a comment - http://www.youtube.com/watch?v=NeE43s-15qE&feature=youtu.be Video proof Log: Sep 30, 2013 2:19:23 PM winstone.Logger logInternal WARNING: Content-length said 9, actual length was 0 Sep 30, 2013 2:19:25 PM winstone.Logger logInternal WARNING: Content-length said 9, actual length was 0 Sep 30, 2013 2:19:27 PM winstone.Logger logInternal WARNING: Content-length said 9, actual length was 0

          Jesse Glick added a comment -

          @suffrage: your problem is unrelated. This button does not support sending parameters to the initial job, so the call to AbstractProject.doBuild simply sends a redirect which is swallowed. The Run button works when the initial job is not parameterized. Please file a separate issue rather than reopening or commenting on this one.

          Jesse Glick added a comment - @suffrage: your problem is unrelated. This button does not support sending parameters to the initial job, so the call to AbstractProject.doBuild simply sends a redirect which is swallowed. The Run button works when the initial job is not parameterized. Please file a separate issue rather than reopening or commenting on this one.

            Unassigned Unassigned
            jrpedrianes Jorge Rodríguez Pedrianes
            Votes:
            11 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: