Jason Flammang
My feedback
5 results found
-
8 votes
An error occurred while saving the comment Jason Flammang
supported this idea
·
-
1 voteJason Flammang
shared this idea
·
-
6 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment Jason Flammang
commented
This would be really great! As an alternative, even the ability to configure a pipeline with a custom Git credential or separate Azure connection so that we could leverage a service account in Azure for performing all of the pipeline automation (promotion branch creation, promotion branch syncing with feature branch, etc.). Currently I have to use my own Azure connection for configuring the pipeline. I like to use my own credentials when tagging work items in a deployment, but for automated actions it would be great to perform that with credentials for a separate service account in Azure so that everyone can distinguish between Git actions taken by a user and automated actions taken by Pipelines.
Jason Flammang
supported this idea
·
-
4 votesJason Flammang
supported this idea
·
-
12 votesJason Flammang
supported this idea
·
This would really help our process. For our organization, having a tagged work item is one of the status checks in ADO for being able to complete a PR into an environment branch. This is currently a manual step that has to be done, not only for the initial PR into the Pipeline but for each auto-created PR through the pipeline.