azure-pipelines-build-task

问题 I need to retrieve a build attachment attached using (##vso[task.addattachment]value) from release summary page (ms.vss-releaseManagement-web.release-details-summary-tab). Please point me to any references to achieve this. Thanks in advance. 回答1: Yes, you need to do followings things to get this: 1.Get the related build id of the release via getConfiguration(): var c = VSS.getConfiguration(); c.onReleaseChanged(function (release) { release.artifacts.forEach(function (art) { var buildid = art

问题 I am getting below error in vsts build. I followed same steps as mentioned here but no luck. 2017-10-12T15:20:56.2694625Z [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project mycompany-vault-client: Failed to deploy artifacts: Could not transfer artifact mycompany-vault:mycompany-vault-client:jar:0.0.1-20171012.152055-6 from/to mycompany-dts-visualstudio.com-mycompany.vault.packages (https://mycompany-dts.pkgs.visualstudio.com/

问题 I am getting below error in vsts build. I followed same steps as mentioned here but no luck. 2017-10-12T15:20:56.2694625Z [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project mycompany-vault-client: Failed to deploy artifacts: Could not transfer artifact mycompany-vault:mycompany-vault-client:jar:0.0.1-20171012.152055-6 from/to mycompany-dts-visualstudio.com-mycompany.vault.packages (https://mycompany-dts.pkgs.visualstudio.com/

问题 I'm getting following error when creating bug item in TFS 2015.2 (On permise) via vso-node-api package, however same code is working perfectly in my VSTS (online) subscription. [Error: Failed Request: Bad Request(400) - TF401349: An unexpected error has occurred, please verify your request and try again.] statusCode: 400 Im using the WorkItemTrackingApi/createWorkItem function in vso-node-api library to create the work item. Following is the sample code I have used to create work items.

问题 In DevOps you can create a dotnet build task where "Path to project(s)" can be set to **/*.csproj to build all the projects. This works just fine, but it (obviously) also builds my *.Test.csproj projects. I found some posts mentioning exclude patterns, so I tried doing the same as in those posts and tried the following combinations: **/*.csproj;-**/*.Test.csproj **/*.csproj;!**/*.Test.csproj **/*.csproj;-:**/*.Test.csproj **/*.csproj;!:**/*.Test.csproj For all attempts I get the following

问题 We have developed VSTS/TFS extension which consists summary page with details generated from our extension task, at the end of build. we have added contribution similar to below in manifest file to add this summary section { "id": "build-status-section", "type": "ms.vss-build-web.build-results-section", "description": "A section contributing to our own new tab and also to existing build 'summary' tab", "targets": [ ".build-info-tab", "ms.vss-build-web.build-results-summary-tab" ], "properties

问题 I would like to be able to add items to the logs displayed during VSTS builds and releases: I've looked at this page and written the following test powershell script $guid = $env:taskGuid write-host "##vso[task.logdetail id=$guid;name=project1;type=build;order=1]create new timeline record" # write-host "##vso[task.logdetail id=new guid;parentid=exist timeline record guid;name=project1;type=build;order=1]create new nested timeline record" write-host "##vso[task.logdetail id=$guid;progress=50

问题 We bought ourselves a Lametric clock (www.lametric.com) which supports displaying messages sent to it through a Web-API. We would like to integrate this into our CI/CD queue. For that we have written a Powershell script, which will send a specified notification. This script works fine, when executed locally. When executed from a (local) VSTS Build Agent, it fails with a status code 417. This is the powershell script: Param ( [Parameter(mandatory=$true)] [string] $BuildName, [Parameter

问题 We recently made a change to our build validation gate on PRs such that the builds expire "immediately" if another commit makes it into master branch before the current PR completes. See here. Even though this change ensures that the master is always accurate/buildable/healthy, this seems to have few negative effects on developer productivity : team members have to continuously keep an eye on their PRs to requeue builds validations. Not only they have to requeue builds manually, but prior to

问题 I'm trying to package one library after build to publish on my VSTS Packages feed. But the task Nuget Packager is not working. I've tried lots of combinations of settings, but I could not make it works. I've tried to package the library using .Net Core and .Net 4.6.2. I'm getting the following error when trying to pack with .Net Core or .Net 4.6.2: ##[error]The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please