What happened:
There is a pipeline defined by below screwdriver.yaml
jobs:
first:
requires: ~commit:release
image: foo
steps:
- bar: foo
second:
requires: first
image: foo
steps:
- bar: foo
The first job is triggered by commit on release branch.
Then, the first job's build is executed with release branch source code.
After first job's build success, the second job is triggered.
However, the second job's build is executed with pipeline branch source code.
Because both builds are reset to same SHA, they are executed with same code.
But they are executed with different branch.
Because of this, if mvn release:prepare is executed in the second job, mvn commits to the pipeline branch not to the release branch.
What you expected to happen:
The second job also executed with release branch.
How to reproduce it:
I can confirm the issue. We've just discovered this in to be happening in our pipeline and found out that it has just been reported.
We'll begin fixing this issue from next week
@jithin1987 @catto are there any updates on this?
@marian-r @kumada626 is now working on this. It's almost done and PR will be created today probably.