microsoft / microsoft/azure-devops-python-api
Enumerating Work Items as part of a release pipeline
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 684
- Forks
- 218
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 1
Description
Hello,
I'm trying to develop a script that will execute as part of a release pipeline. The script should enumerate work items returned by a stored query and perform release activites per each work item using some custom fields included in the work item itself.
Looking at the API documentation it seems that I will need to generate a personal access token to give my script access to the Azure DevOps environment to do this activity but my question is - why? If I'm running the python as a release task, technically I've already got "access" by the very nature of the release pipeline itself running as an agent task? Do I really need to generate another token or can I just use the context of the agent? And if so, how?
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
The issue names no repository files or tests; start with the API documentation for personal access tokens and the release-task agent context described in the question. Document whether a release pipeline can enumerate stored-query work items and access their custom fields without a separate token, and explain the supported authentication path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- api, authentication, devops
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100