web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Second release pipeline

(0) ShareShare
ReportReport
Posted on by 4,131

Hi,

I have one release pipeline to automatic upload the deployable package to LCS. And I clone a second one which exactly the same, only difference it was triggered from different build definition. 

But the second release pipeline always failed during the update LCSAssetID variable.

>>>>>>>>>>>>>>>>>>>>>>>>>>>

2020-01-07T15:51:26.1562783Z Invoke-RestMethod : {"$id":"1","innerException":null,"message":"VS402904: Access denied: User Project Collection Build 
2020-01-07T15:51:26.1562969Z Service (D365SpinService) does not have manage releases permission. Contact your release 
2020-01-07T15:51:26.1563078Z manager.","typeName":"Microsoft.TeamFoundation.Framework.Server.UnauthorizedRequestException, 
2020-01-07T15:51:26.1563378Z Microsoft.TeamFoundation.Framework.Server","typeKey":"UnauthorizedRequestException","errorCode":0,"eventId":3000}
2020-01-07T15:51:26.1563476Z At D:\a\_temp\3327ab13-f039-4638-b397-371a6739fb73.ps1:18 char:14
2020-01-07T15:51:26.1563550Z + ... updatedef = Invoke-RestMethod -Uri $url -Method Put -Body $json -Cont ...
>>>>>>>>>>>>>>>>>>>>>>>>>
Any idea?
 
Thanks,
I have the same question (0)
  • nmaenpaa Profile Picture
    101,160 Moderator on at

    What exact step is it that fails? Can you share any more logs?

    I would start by narrowing down the possible cause for the problem. If you make this new release pipeline to be triggered from your original build pipeline, does it work?

  • Verified answer
    Joris dG Profile Picture
    17,775 on at

    I can tell this is your own code that you or someone added to maintain the LCS asset ID from the upload task, to be used in a later stage(s). This is essentially a call into the Azure DevOps API to store that. (Similar to what's explained in this blog: ariste.info/.../ )

    However, this requires proper permission, as well as making sure you update the right release. So you need to check the code that does this, and ensure it either dynamically gets the IDs it needs (definition, project, etc.) or adjust them if they're hardcoded. Secondly, review the permissions for the pipeline (it's always at the top right under the ... button) and make sure the build service user has "manage releases" permission.

  • Yuji Profile Picture
    4,131 on at

    Grant the build service user "manage releases" permission resolved the issue.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 551 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 450 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 278 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans