azure-pipelines-release-pipeline

问题 I have separate existing code repositories- One for Angular UI and one for .NET 4.7 API layer. In the manual process, The compiled UI code is placed in wwwroot folder after dotnet publish is executed, and the artifacts are deployed to an Azure App service. While trying to implement CI using Azure DevOps, I had to create two build pipelines for UI and BackEnd. In the release pipeline, it looks like I have to unzip the artifacts, write a copy step to UI artifacts into wwwroot and then again zip

问题 I have a build steps like: - ... - npm install - npm start sb:server (start http-server to serve static files) - npm run e2e By the npm start sb:server; it starts the server and it hangs... and doesn't go the next phase which is npm run e2e. I would like to add a condition to npm run e2e that it should just start without looking previous phase state (failed or succeeded). I have checked the https://docs.microsoft.com/en-us/vsts/pipelines/process/conditions?view=vsts#job-status-functions I can

问题 I am setting up an Azure DevOps release pipeline with three different stages. As shown in the following screenshot a new release has already started even though the preceding release is still running. Is there a way to configure a release to complete all its stages before the next in the queue is getting started? 回答1: For more readable, I will talk based on the pic you shared in the question. In fact, in the release which has multiple stages, the stages are independent of each other. As you

问题 I have configured and scheduled only release definition on VSTS for Azure solution deployment which is having PowerShell tasks. But I want to open a bug or work item in VSTS if release/ deployment fails. Is it possible in VSTS. 回答1: Yes, it’s possible for VSTS to create a bug if a release failed. Add another PowerShell task in the end of your release definition to create a bug if the previous task fails. Detail settings for the PowerShell task as below: Select Only when a previous task has

问题 Could you please give me some advise on how to deal with this issue. Build Pipeline npm install package.json "dependencies": { "cypress": "^3.4.1" } Release Powershell command npm ./node_modules/.bin/Cypress run The cypress npm package is installed, but the Cypress binary is missing. 2019-10-07T18:04:59.5720120Z We expected the binary to be installed here: There are some examples on how to cache ~/.npm but nothing seems to work so far. Examples on how to include cypress.io in your vsts are at

问题 I'm using PowerShell inline task in the release pipeline to deploy the respective zip file to the Azure App Service, but im unable to achieve it due to the below error. Can you please let me know if there is any thing that im missing here. I'm getting below error Invoke-RestMethod : Path 'D:\a\r1\a_CI-VI-Maven/DeployPackages/marnet.zip' resolves to a directory. Specify a path including a file name, and then retry the command. Below is the script that im using: $username = "username" $password

问题 I'm trying to build and publish certain folders of a project and deploy them to remote server using Azure DevOps. My Copy files task and Archive copies everything from TFS instead of the content I want to build and deploy. The last two screenshots display the Build folder getting published and the last one is the folder which is supposed to be Published. 来源： https://stackoverflow.com/questions/64173144/vsts-azure-devops-trying-to-build-and-save-only-certain-folders-but-everything

问题 I'm trying to build and publish certain folders of a project and deploy them to remote server using Azure DevOps. My Copy files task and Archive copies everything from TFS instead of the content I want to build and deploy. The last two screenshots display the Build folder getting published and the last one is the folder which is supposed to be Published. 来源： https://stackoverflow.com/questions/64173144/vsts-azure-devops-trying-to-build-and-save-only-certain-folders-but-everything

问题 In the Release workflow in Azure DevOps Services, while setting up Continuous Deployment trigger, there is this option which 'The build pipeline's default branch' . I don't understand what it means and how can I view the default branches for different pipelines in my project. Any reference to documentation on this aspect will also help This appears in a couple of other places also in the Pipelines, but I can't remember it now. Thanks, 回答1: As this document describes the default branch is

问题 In the Release workflow in Azure DevOps Services, while setting up Continuous Deployment trigger, there is this option which 'The build pipeline's default branch' . I don't understand what it means and how can I view the default branches for different pipelines in my project. Any reference to documentation on this aspect will also help This appears in a couple of other places also in the Pipelines, but I can't remember it now. Thanks, 回答1: As this document describes the default branch is