azure-devops

问题 When pull requests are created, their commit message is always like "Merged PR### from {branch name} into {target branch name}" I keep amending commit messages and this is a bit tiring. I rely on the commit messages to keep track, so the automatic messages present a problem. 回答1: This is a feature of Azure DevOps, the purpose is making it clearly to describe what happened for each commit. For the commit message with a merged commit by pull request, the default commit message is defined by the

问题 When pull requests are created, their commit message is always like "Merged PR### from {branch name} into {target branch name}" I keep amending commit messages and this is a bit tiring. I rely on the commit messages to keep track, so the automatic messages present a problem. 回答1: This is a feature of Azure DevOps, the purpose is making it clearly to describe what happened for each commit. For the commit message with a merged commit by pull request, the default commit message is defined by the

问题 Can't believe I'm stuck with a LOGIN :( hate when this happens. Can somebody enlight me how to connect TF.EXE by using PAT password or in the best case an OAuth token? I might add that I already have a Pat token and an OAuth token, not a problem while trying to get those, but every time I try this example: TF.exe workspaces /collection:xxxx.visualstudio.com/xxxx /loginType:OAuth /login:.,MyPatTokenOrMyOauthToken /noprompt I get the following response: TF30063: You are not authorized to access

问题 I have setup 2 private agents under agent pool but when I run the pipeline I want a specific agent to run the pipeline but its not happening. How to select or where to select specific agent to run the pipeline with YAML configuration. 回答1: You need to specify a demand with your agent name you want. you enter the demand in the yaml after the pool name: pool: name: Private demands: Agent.Name -equals Test More info you can find here. Without YAML the demands exist under the Options tab: Or per

问题 I'm looking for a way to add my own attachments to test results so that I can see them after a build has completed here... I would like to add these programmatically, during a build and after a test has failed. The attachments will be screenshots. Is this possible? I had a quick look at the API reference but this looked to be concerned with adding attachments to existing test 'runs', or on the build, the side was for creating build definitions and triggering them. I may have missed it but I

问题 I'm a developer whose transitioning into Devops. By observation, I've noticed that a lot of dev shops have started using Octopus Deploy and Azure Devops Services (AzDo, formerly VSTS), or they are starting new projects to setup devops ci/cd pipelines AND they spec to use both tools. I've been through some quick training for both tools and though they aren't perfectly the same, AzDo seems to offer all of the same features as Octopus Deploy. So, my question is if a company is already using AzDo

问题 I want a stage in an Azure DevOps pipeline to be executed depending on the content of a variable set in a previous stage. Here is my pipeline: stages: - stage: plan_dev jobs: - job: terraform_plan_dev steps: - bash: echo '##vso[task.setvariable variable=terraform_plan_exitcode;isOutput=true]2' name: terraform_plan - stage: apply_dev dependsOn: plan_dev condition: eq(stageDependencies.plan_dev.terraform_plan_dev.outputs['terraform_plan.terraform_plan_exitcode'], '2') jobs: - deployment: "apply

问题 I am trying to create a prerelease build for a .net-standard 2.0 library in VSTS. I have created a build with the following steps dotnet restore version 2 dotnet build version 2 dotnet pack version 2 nuget push version 2 When I use the environment variable (PackageName) as $(Build.BuildNumber)-beta as my pack version. The pack fails with the error BuildName_2018.7.11.1-beta is not a valid version string . I have previously used this environment variable as my pack version in .net-framework

问题 I have a Azure DevOps pipeline with a local nuget package to a local artifact repo, and then a push to nuget.org. It however is not updating the version and remains at 1.0.0-{build_ver} in the local azure DevOps project artifacts (whilst version is stuck the build_ver of the package increments as expected), but when it tries to push to nutget it fails as its the same 1.0.0 version and ignores the 1.0.1 in the project file. Any pointers please - how can i get the version defined in the csproj

问题 I have a synchronization between Azure DevOps and Github to sync the Github repo with the repo in Azure Devops. End of last year everything works fine. This year the synchronization do not work anymore. The failure message was fatal: could not read Password for 'https://$(XXXXXXXXXToken)@yyyyyy.visualstudio.com': terminal prompts disabled ' I have forgotten, that the PAT expires on 31.12.2019. So I recreated the pipeline, instead of just changing the expiration date of the PAT. facepalm . My