Same issue here after upgrading Jenkins to 1.523 and Build Pipeline plugin to 1.3.5.
Don't see any related errors in the logfile though.
Clicking on 'Run' button in Pipeline view does not work anymore.
And retrying a build, in the pipeline view, does show the new build anymore.

I have the same issue as described in post above, same environment.

I am using Build Pipeline Plugin 1.3.5, and seeing the same issue.
Don't see the retry build option.
And the 'Run' button on top of the view do not start the pipeline job.

We have the same with build pipeline plugin 1.3.5 and Jenkins 1.525. I am putting this on blocking, since the run button is the key of the plugin. If that does not work, the plugin is not usable.

I did a quick research. Run button works with jobs which require no parameters, jobs with parameters do not work.

Same problem here with Build pipeline plugin 1.3.5 and Jenkins 1.525. Has anyone tried to downgrade the Jenkins or the plugin version?

We don't have any parameters and Run button still doesn't work, so that's not the cause.

Keep in mind, that might need to clear the browser cache. I "fixxed" one of my BP probems dropping my browser cache %-/

The last known working version is 1.509.2 (LTS) plus BP 1.3.3. All other combinations starting from 1.519 - 1.5.24 or so didn't work. We tried a lot, including nightly builds of the BP plugin. IMHO all BP plugin versions since the switch to jquery don't work.

It might be a good idea to follow https://github.com/jenkinsci/build-pipeline-plugin/commits/master before starting effort in try & error...

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.

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.

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

@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

@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

@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.