When I retrigger manual steps, whether the previous run succeeded or failed, the UI does not update to reflect the new build. It continues to show the previous build time and status, despite the builds being correctly triggered. The initial job, or jobs that are run automatically after the completion of another job behave as expected. This behaviour appears to be a regression between 1.4.4 and 1.4.5 of the plugin

To reproduce, please use the attached DSL script to create the sample pipeline. You might need to adjust the variables at the top to suit.
1. Trigger a pipeline build
2. Compile and deploy steps should run
3. Manually trigger the Deploy QA step
4. Manually retrigger the Deploy QA step
5. The spinner appears, but on a page refresh the data for the previous run appear
6. Checking the build history shows that the Deploy QA job has run twice