I have set up my pipelines with the following approach (we do canary releases):
- On master pipeline, bitbucket will push a tag and commit the new version with [skip ci] preffix.
- I have a webhook to identify tags creation and run staging deployment pipeline on master
- After successful tests on staging, we decide to deploy master on canary.
- We also use JIRA automation to identify deployments on issues to do some transitioning (canary deployments will transition issue from Done to Canary, for instance)
The problem we are facing happens when we have some PRs merged before step 3 and not all expected JIRA issues are listed as deployed to canary.
Example:
- Current version in master is 1.0.0
- Latest commit on master is also the commit on deployments on staging and canary
- 3 PRs are merged in same day, which generates versions 1.0.1, 1.0.2, 1.0.3
- All of the versions above were deployed to staging, latest commit on staging is the 1.0.3 commit version;
- We decide to deploy canary. Only issue between 1.0.2 and 1.0.3 is listed as issues deployed, although issues from 1.0.0 (last canary version) to 1.0.3 should be listed there.
How can I make this work? Is this approach possible to be used?
