Use the standard trick for BuildAbortionStage

[jglick]

Summary

Avoids using non-sandbox-friendly methods to abort previous builds, using the standard workaround for JENKINS-43353. (Requires the pipeline-milestone-step plugin.) jenkinsci/workflow-job-plugin#200 would be nicer.

Submitter's Pledge

Reviewers, I have verified the following to the best of my knowledge:

• I have added unit test cases for the changes where applicable.
• I have updated CHANGELOG.md with the new target version (or with the Unreleased tag) and updated the version comparison url in the file.
• I have updated documentation in README.md at the repo root and all of the applicable README.md files under docs/** along with necessary version change for code samples in those docs where applicable.
• I have read and fully understand the process for submitting a pull request to the codebase.

Review Recommendation

Not sure whether this is tested realistically.

[NickLiffen]

@jglick if you see here:

https://github.com/EliLillyCo/jenkinsdsl/blob/e6ee83976ddb29cd46d28fee63b8b4ccd7c59930/test/src/com/lilly/cirrus/jenkinsdsl/core/BuildAbortionStageSpec.groovy

I think most of these can be deleted, but I would like some tests around how this works if that's okay 👍

[jglick]

I would like some tests around how this works

Your test system is over my head I am afraid. The actual Pipeline code is covered by jenkinsci/pipeline-milestone-step-plugin#12.

[jglick]

jenkinsci/workflow-job-plugin#200 has been released; I would recommend that now instead.