Closed leandrohinz closed 2 years ago
What permissions did you give the pat
Thank you maik for your quick answer..in fact the issue was the permissions and scope of the PAT, but i got another question.. can i 'pass' the environment like we can 'pass' the branch?.
Do you mean the environment you are triggering?
Exactly, i mean i got a "master pipeline" that triggers another build pipelines, one of them is called "claims party policy configurations" and that build got a variable called environmentArtifact, and that value is setteable at queue time, so if i want to build to QA i changed that value before the build and when the build ends it triggers the CD to the QA stage, so how can i ´pass´ this environmentArtifact value from my "master pipeline" in the task azure trigger to the build (like you do when you "pass" the branch )
I get your question variable setting isn't supported at the moment. Will try to look at that this week.
Great Maik, i'll stay tuned.
Hi maik, any update on this? thanks!.
Yes, I almost have a beta version ready. Would you like to beta test ? If yes could you send your organization name?
Of course maik, its https://oms-fort.visualstudio.com/ thank you in advance!
new extension version is beign published at the moment.
Hi Maik, can you help me with this?, i added the task Trigger Pipeline because i need to trigger a build pipeline in a task of a release pipeline in one of my projects, i was able to create the service connection for the service connection i was able to create the PAT without problems, But when i tried to select the Project and Build Definition fields it not show anything in the dropdown list: Can you please help me out with this? Heres the service connection settings:
If i hardcode the project name, the build definition and the branch i got this error: (##[error]The remote server returned an error: (401) Unauthorized)