azure-pipelines

问题 I'm trying to add a new comment to a work item which mentions a user, but using the traditional "@adamh" as you would do on the website does not seem to work via the API. The data updates fine, however the "@adamh" is just plain text, I need to be able to somehow chuck an identity into here. Can anyone point me in the right direction? Thanks! A snippet is here const vsts = require('vso-node-api'); const item = require('vso-node-api/WorkItemTrackingApi') const ti = require('vso-node-api

问题 I want to get the data from the variable Build.Repository.LocalPath and use it in my Dockerfile, but it shows me and error. This is my dockerfile: FROM microsoft/aspnet:latest COPY "/${Build.Repository.LocalPath}/NH.Services.WebApi/bin/Release/Publish/" /inetpub/wwwroot I get this error: Step 2/9 : COPY "/${Build.Repository.LocalPath}/NH.Services.WebApi/bin/Release/Publish/" /inetpub/wwwroot failed to process "\"/${Build.Repository.LocalPath}/NH.Services.WebApi/bin/Release/Publish/\"":

问题 When configuring a local build agent on a Windows 2016 server, I use the following proxy config settings: .\config.cmd --proxyurl http://192.3.4.5:8080 --sslskipcertvalidation This allows the build server to connect to Azure DevOps behind the proxy without issues, however the powershell build is having trouble connecting out to the internet. I solved this by setting an environmental variable at the beginning of the build command as such: $env:http_proxy = "192.3.4.5:8080" The final issue is a

问题 I'm configuring my build pipeline for an Android project. So far, all of my steps are working perfectly on Hosted VS2017 agent, including fetching the code, building with gradlew, publishing the artifact and deploying it to AppCenter. However, on Hosted Ubuntu 1604, there are a few problems with gradlew step. On VS2017 agent, this works with just: .\gradlew assembleDebug On Ubuntu 1604, this is what I'm having right now: chmod 775 gradlew chmod 775 /usr/local/lib/android/sdk --> The fix I'm

问题 I'm configuring my build pipeline for an Android project. So far, all of my steps are working perfectly on Hosted VS2017 agent, including fetching the code, building with gradlew, publishing the artifact and deploying it to AppCenter. However, on Hosted Ubuntu 1604, there are a few problems with gradlew step. On VS2017 agent, this works with just: .\gradlew assembleDebug On Ubuntu 1604, this is what I'm having right now: chmod 775 gradlew chmod 775 /usr/local/lib/android/sdk --> The fix I'm

问题 Is it possible to have a single release pipeline with multiple artifacts that will trigger separate stages conditionally. Example: (Build Artifact 1) Build tags of Web (Build Artifact 2) Build tags of Identity When i setup my release pipeline I create one pipeline and add the (Build Artifact 1) -> Web Stage (Build Artifact 2) -> Identity Stage both of those artifacts are set trigger a release automatically and set to After Release The problem I have is that when I queue the build for (Build

问题 Is it possible to have a single release pipeline with multiple artifacts that will trigger separate stages conditionally. Example: (Build Artifact 1) Build tags of Web (Build Artifact 2) Build tags of Identity When i setup my release pipeline I create one pipeline and add the (Build Artifact 1) -> Web Stage (Build Artifact 2) -> Identity Stage both of those artifacts are set trigger a release automatically and set to After Release The problem I have is that when I queue the build for (Build

问题 I have a Deployment Group with X number of servers. I've created and set up my Release Pipeline to work as expected. When I run it, it deploys to all servers under my Deployment group. (I do filter by specific Tags but that's irrelevant) What I need now, is to be able to filter/exclude servers on the fly during deployments (for example: deploy only on the first server and leave the rest unchanged) Something like the below (screenshot taken from Octopus which supports this functionality) I'm

问题 I have a Deployment Group with X number of servers. I've created and set up my Release Pipeline to work as expected. When I run it, it deploys to all servers under my Deployment group. (I do filter by specific Tags but that's irrelevant) What I need now, is to be able to filter/exclude servers on the fly during deployments (for example: deploy only on the first server and leave the rest unchanged) Something like the below (screenshot taken from Octopus which supports this functionality) I'm

问题 I have two pipelines, release and prerelease. In release pipeline version set up like this, the counter for the patch and manually set major/minor version: variables: solution: '**/*.sln' buildPlatform: 'Any CPU' buildConfiguration: 'Release' majorVersion: '1' minorVersion: '1' patchVersion: $[counter(format('{0}.{1}', variables['majorVersion'], variables['minorVersion']), 0)] productVersion: $[format('{0}.{1}.{2}', variables['majorVersion'], variables['minorVersion'], variables['patchVersion