harness / harness/backstage-plugins
[Bug]: Selective stage execution for multiple services deployment
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behaviour
When a user configures the serviceID , it should show all executions/deployments where that particular service has been deployed
Actual behaviour
So currently we configure the latest 5 pipelines that deploy that serviceID, and show their executions but there can be a case where the particular pipeline deploys multiple services and has done selective stage execution in which that Service hasn't been deployed but it will appear in the execution list.
Contributor guide
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
Trace the serviceID execution-listing path described in the issue, starting with how the latest five pipelines and their executions are selected. Verify how selective stage execution records identify deployed services; done means executions appear only when the configured service was actually deployed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100