SSWConsulting / SSWConsulting/SSW.Rules
DevOps - Investigate why staging release pipeline is not triggered
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
cc @pierssinclairssw @tombui99
When the staging content branch is changed, a new build is triggered but not a release. It is not clear why this happens.
- Investigate why the staging release pipeline is not triggered automatically when content is changed
Thanks,
-Brady
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or pipeline entry points are named. Start by locating the staging content branch build and release pipeline configuration, then trace why a content change triggers the build but not the release; done means the cause is documented and the automatic staging release behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100