I did face a very similar issue.
In our project we create pipeline jobs per branch with Job DSL for a lot of microservice projects. We are using the milestone plugin as well and were very happy with this. Accidentally a change to our Job DSL script caused the seed job to delete all pipeline jobs. After fixing the issue the jobs were created again, causing all jobs to fail, because they were going to start at build number 1.
The output looks like this
[Pipeline] milestone
Trying to pass milestone 1
Canceled since build #6 already got here
[Pipeline] End of Pipeline
To reproduce this:
- Create a job named "test-pipeline"
- add:
stage "BUILD"
echo "I do something"
stage "RELEASE"
milestone 1
input message: 'Do you want to release me?', ok: 'Go, release, go!'
milestone 2
echo "Yes, I am released!"
- Just try the job a few times and accept the input prompt
- The milestone plugin behaves as expected
- Now create the job again, with exactly the same name and pipeline DSL script
- Now the job fails because the build counter is not reset and the job "thinks" the build is older than a previous one of the first, deleted job
This currently makes the usage of the milestone plugin useless for us. Or is there anything we can do about it?
Thank you
I did face a very similar issue.
In our project we create pipeline jobs per branch with Job DSL for a lot of microservice projects. We are using the milestone plugin as well and were very happy with this. Accidentally a change to our Job DSL script caused the seed job to delete all pipeline jobs. After fixing the issue the jobs were created again, causing all jobs to fail, because they were going to start at build number 1.
The output looks like this
To reproduce this:
This currently makes the usage of the milestone plugin useless for us. Or is there anything we can do about it?
Thank you