microsoft / microsoft/azure-devops-python-api
Trigger the release with build id makes the pipeline stuck
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 684
- Forks
- 218
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 1
Description
I've tried to trigger a build and get the id of build, then trigger a release pipeline using this id. When I trigger the release pipeline, I did not wait for the completion of build. Now, the release pipeline is stuck.
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
Start by reproducing the sequence described: trigger a build, obtain its build ID, and trigger the release pipeline before the build completes. Inspect the Azure DevOps build and release API behavior around that ordering. Done means the release pipeline handles the build ID without becoming stuck, with the expected behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- api, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100