Steps to reproduce:
- Create a build pipeline with at least two stages, the second of which adds Actions to a build. For example, the git-plugin will attach a hudson.plugins.git.GitTagAction to the build to say what revision was built.
- Run the pipeline
- Re-run the second stage of the pipeline
- One actions in the summary page of the build from the git plugin
- Two actions! The previous builds action and the current builds (see attached screenshot)
Marking as major because this results in breaking the TestNG publisher plugin - it relies on actions being persisted in builds to show reports and trend data. When actions are copied, the data is corrupted, and trends are overridden. This could potentially break other plugins in the pipeline as well.