-
I have added a task to my release pipeline to update a build pipeline variable called CustomVersion from "00" to "99". I have set the permissions for my [ProjectName] Build Service ([Name]) account to allow both "Edit release pipeline" under the Release Pipelines tab and separately "Edit build pipeline" under the Build Pipelines tab. There is no option for "Edit build definition" available to me anywhere that I can find. I have tried running the job from a private agent, windows-latest agent, and ubuntu-latest agent. The logs of the task always look more or less like the following:
I have read the Wiki more than once and I'm still not getting it. Has something in DevOps changed since the documentation was written? Am I missing something? Any help you can offer would be most appreciated. Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
I have re-written the documentation multiple times for this issue, not changing the fundamentals, but trying to explain it in a clearer way. It is hard to explain it seems. The summary is the account the build is running as (probably the project or project collection build agent account) needs to be given permission to edit the build, release or pipeline definition template. By default all accounts only have read access to the templates. This is required as the variables are stored on the underlying template/definition no the build run. This permission can either be set for a single pipeline or all definitions (use manage security on the ellipsis menu) |
Beta Was this translation helpful? Give feedback.
I have re-written the documentation multiple times for this issue, not changing the fundamentals, but trying to explain it in a clearer way. It is hard to explain it seems.
The summary is the account the build is running as (probably the project or project collection build agent account) needs to be given permission to edit the build, release or pipeline definition template. By default all accounts only have read access to the templates. This is required as the variables are stored on the underlying template/definition no the build run.
This permission can either be set for a single pipeline or all definitions (use manage security on the ellipsis menu)