azure-pipelines-release-pipeline

Azure Virtual Machine Scale Set VSTS Deployment Group

末鹿安然 提交于 2021-02-19 06:28:06
问题 Is it possible to have the vm's in a VMSS be in a deployment group inside of VSTS? Could I provision a vm with the deployment group, save its disk image, and use that as the image for the vm's in the scale set? That way when a new VM is created it will already have the vsts agent on it. But, will the authentication still work against VSTS? I know it uses a PAT, I feel like there could be issues there. Also, if new vm's "scale" up, how would they be able to get the latest version of the build?

VSTS Build not generating latest bin binaries

孤街浪徒 提交于 2021-02-15 07:50:18
问题 I am using TFS 2018 CI pipeline for MVC project, also I added the project's bin files into the TFS, there is no problem with the pipeline, its getting succeeded and artifact is generated successfully but the main problem is that if I made any changes in code related to project's DLL, the CI pipeline's build solution not generating its own latest bin file Until or unless I manually check Out the project.dll file and than check In the file than pipeline will pick the changes, what I am missing,

Azure DevOps REST API to create a release definition

孤者浪人 提交于 2021-02-11 16:52:16
问题 I'm trying to create a release definition by using Azure DevOps REST API. I've created a json file which has configuration details for the request. I'm getting the below error, while creating the release definition. { "$id": "1", "innerException": null, "message": "Workflow of deploy job 'Run on the agent' in release pipeline stage 'development' is invalid. Add valid tasks and try again.", "typeName": "Microsoft.VisualStudio.Services.ReleaseManagement.Data.Exceptions.InvalidRequestException,

Azure DevOps REST API to create a release definition

人走茶凉 提交于 2021-02-11 16:51:29
问题 I'm trying to create a release definition by using Azure DevOps REST API. I've created a json file which has configuration details for the request. I'm getting the below error, while creating the release definition. { "$id": "1", "innerException": null, "message": "Workflow of deploy job 'Run on the agent' in release pipeline stage 'development' is invalid. Add valid tasks and try again.", "typeName": "Microsoft.VisualStudio.Services.ReleaseManagement.Data.Exceptions.InvalidRequestException,

Azure DevOps Cancel deployment of stage when deploying another stage

岁酱吖の 提交于 2021-02-10 18:33:19
问题 We currently have our Azure DevOps release setup in the following way: What I'm trying to accomplish is to cancel the 2:00 PM deployment if the 9:00 AM deployment triggers, as well as cancel the 9:00 AM deployment if the 2:00 PM deployment triggers since we don't really want to deploy the same code twice, or even deploy the previous day's code the following day. Does anyone know if a way to do this in Azure DevOps? I've done a lot of searching for extensions, etc. to see if I can find

Azure DevOps Cancel deployment of stage when deploying another stage

好久不见. 提交于 2021-02-10 18:32:18
问题 We currently have our Azure DevOps release setup in the following way: What I'm trying to accomplish is to cancel the 2:00 PM deployment if the 9:00 AM deployment triggers, as well as cancel the 9:00 AM deployment if the 2:00 PM deployment triggers since we don't really want to deploy the same code twice, or even deploy the previous day's code the following day. Does anyone know if a way to do this in Azure DevOps? I've done a lot of searching for extensions, etc. to see if I can find

AzureDevOps Release pipeline with multiple artifacts

こ雲淡風輕ζ 提交于 2021-02-08 13:33:20
问题 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

AzureDevOps Release pipeline with multiple artifacts

坚强是说给别人听的谎言 提交于 2021-02-08 13:33:07
问题 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

How exclude Deployment Group Target from Release on the fly

大城市里の小女人 提交于 2021-02-08 10:01:45
问题 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

How exclude Deployment Group Target from Release on the fly

北城余情 提交于 2021-02-08 10:01:17
问题 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