We are pleased to announce the availability of version 1.2.1.
The release addressed bugs and enhancements.
Retry Failed Jobs
Restrict the Trigger Button to the Latest Build
If a job in the pipeline fails, the job will now display a “Retry” button. This allows the user to retry this job, with the parent build remaining as the trigger and continue the build pipeline.
When configuring a build pipeline view a new option “Restrict Trigger to the Most Recent Build” has been added.
If set to “Yes” it will only allow the most recent build pipeline to display a “Trigger” button.
If set to “No” all builds displayed on the view will have a manual trigger button.
The following defects have been resolved. Remaining defects are visible from the google code issue tracker (http://code.google.com/p/build-pipeline-plugin/issues/list).
|33||plugin interfering with job renames/deletes|