User Profile
Jacob_Peterson
Copper Contributor
Joined 3 years ago
User Widgets
Recent Discussions
ServiceHooks: Run Stage State Changed Event - Include Array of Environment Names from Deployment Job
It would be SO helpful if the ‘run stage state changed’ event payload included environment names from the deployment jobs. Perhaps it makes sense to include an array detailing the Jobs that were completed in the Stage and if it was a deploy job, include the environment name there. This would make life so much easier and would reduce the number of API calls I have to do after the fact to find this information. My requirement is to “Detect” prod deployments and look up the commits that were completed between this current prod deployment and the last. We do this to calculate the Delivery Lead Time. My problem is that the Stage name is free-form text and can be ANYTHING like “DeployCode” or "Release". How am I supposed to know that is Prod?514Views0likes0CommentsAllow Pipelines to have Tags/Metadata like Azure Resources
We need the ability to add metadata to Azure DevOps Pipelines such as “Domain”, “Capability”, “Team”, “SRE Owner”, etc. This information needs to be available in the pipeline/ api response. It would also be useful to have the ability to filter/search by this in the UI, but that is not important for my immediate use case. Currently, to obtain this data, we are maintaining a separate reference table. It is not ideal.2KViews0likes2CommentsEnhance YAML Pipelines 'Changes' API Endpoint to allow user to specify the 'artifact'
There exists an API endpoint that allows a user to request the changes for a Classic Release run and pass the Artifact Alias that they would like the changes from: https://vsrm.dev.azure.com/{collection}/{project}/_apis/Release/releases/{releaseId}/changes?artifactAlias={artifactAlias} If a team replicates this type of pattern in YAML pipelines where there is a build pipeline (or multiple) and then a multi-stage YAML 'release' pipeline, there is no way to get the changes from the build artifacts. You can request the changes from the API for the multi-stage 'release' pipeline, but you cannot get the changes for the build pipelines IN THE CONTEXT OF the currently releasing stage. The build artifacts are specified in the release pipeline in the resources: resources: pipelines: - pipeline: myBuildPipeline source: myBuildPipeline trigger: branches: include: - main531Views0likes0CommentsImplement Paging on Service Endpoints REST API endpoint
https://learn.microsoft.com/en-us/rest/api/azure/devops/serviceendpoint/endpoints/get-service-endpoints?view=azure-devops-rest-7.0&tabs=HTTP This REST API Endpoint does not have paging enabled. Please implement as soon as possible. It only returns the first 100 service connections. It does not have a continuation token included in the response like other endpoints.565Views0likes0CommentsRe: Empowering Teammates to Dynamically Set Azure Subscriptions in Azure DevOps Pipelines
Dheeman If you do not have one already, create an AzureRM Service Connection in Azure DevOps. Grant the Service Principal the appropriate role in each subscription that you want it to read from (likely reader would be sufficient). Copy the Service Connection's ID to the clipboard. In your pipeline, add this new powershell task. This will "target" the Service Connection to the subscriptionId that was passed in. - pwsh: Write-Host "##vso[task.setendpoint id={YOUR SERVICE CONNECTION ID HERE};field=dataParameter;key=subscriptionId]${{ parameters.SubscriptionId }}" displayName: Set Subscription 3. Then change the task type for your script that you wrote. Use the Azure CLI task with powershell and use this Service Connection that you created. Now it should authenticate to the subscription you passed in and execute your script in that context. It will not matter what you logged into last on your local machine.1.3KViews0likes2CommentsRe: Empowering Teammates to Dynamically Set Azure Subscriptions in Azure DevOps Pipelines
Set a parameter in your pipeline that allows the user to specify a subscriptionId. Then use this subscriptionId parameter in your script. Have the other teammates invoke the pipeline with: az pipelines run --name AssessmentTool_Report-CI --org https://dev.azure.com/DheemanDas --project test --parameters SubscriptionId={sub}1.4KViews0likes4CommentsRe: Is there an API that list all project level Azure DevOps Groups?
You can get all Groups from this endpoint: https://vssps.dev.azure.com/{collection}/_apis/graph/groups?api-version=7.1-preview Then check in the principal name of each group object for the project name like: [My Project]\\My_Project_Prod_Approvers1.3KViews0likes0Comments
Groups
Recent Blog Articles
No content to show