forcedotcom / forcedotcom/devops-center-feedback

Not able to promote work items past first stage: Rebase failures

Open
#220 12 comments 0 reactions 0 assignees View on GitHub
INVESTIGATION P3
Dominant language
No language data
Stars
61
Forks
2
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
After deploying an approved work item to the first stage of our pipeline we try to promote the work item to the second stage and receive the error "Promotion Blocked: Promotion blocked due to dependency". We didn't receive any errors in the UI when promoting to the first stage - everything displayed as successful. Upon reviewing Activity History we noticed an error stating "Rebase of WI-XXXXXX branch from QA branch failed".

Once this error occurs the pipeline is stuck. I tried manually rebasing the branch and even though that is successful, the pipeline continues to throw the dependency error.

**To Reproduce**
Steps to reproduce the behavior:
1. Get 2 work items to approved state (New account field in each work item)
3. Promote one work item to first stage: Integration
4. Promote second work item to first stage: Integration
5. Try to promote second work item to second stage: UAT
6. Review error: Promotion Blocked
7. Click on Activity History
8. Review Rebase errors from Promotion to first stage
...

**Expected behavior**
After promoting to the first stage, we should be able to select any of the available work items and promote to the next stage

**Screenshots**
If applicable, add screenshots to help explain your problem.
![Screen Shot 2022-10-03 at 11 01 33 AM](https://user-images.githubusercontent.com/18169572/193625593-487b243f-fb79-463c-b0cf-00107760ff29.png)
![Screen Shot 2022-10-03 at 11 02 07 AM](https://user-images.githubusercontent.com/18169572/193625595-8731c665-f41e-4d87-b604-9bb35ade3931.png)
![Screen Shot 2022-10-03 at 11 02 44 AM](https://user-images.githubusercontent.com/18169572/193625596-1e70583a-2c4a-4b54-b74b-b9a5611fe173.png)

**Additional context**
Repository is set up under an organization. We created a brand new repository with branches for the test and checked settings to ensure we didn't have anything blocking rebases.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.