azure-pipelines-release-pipeline

问题 I have an asp.net core website that I'd like to deploy to an on-prem IIS server using devops (VSTS) pipeline. The build pipeline works fine but I've hit a problem when configuring the release pipeline. Process followed: Create new Release Pipeline - selected "IIS website deployment" as the template On the "Deployment group job" blade there's a drop-down that requires selection of a "Deployment group". Clicked the cogs icon to the right of this drop-down and created a new deployment group

问题 I have to add additional parameter to application manifest xml file while deploying to cluster. There is a release pipeline configured in VSTS to which I have to add a task. How to achieve this ? Should I have to use Powershell inline script ? If so how can I modify file in the artifact directory ? @Karthick, Thanks for your answer , but I am facing issues while saving the xml. I did set the Working folder as $(build.artifactstagingdirectory) $appManifestFile = $(build

问题 I am building a release pipeline which creates and populates a table in Azure Table Storage if it doesn't yet exist. My Powershell file runs locally on my machine, but when I check it in to VSTS and execute it in the Release pipeline in an 'Azure Powershell' step it fails. Here is the relevant script from the ps1 file: $ctx = New-AzureStorageContext -StorageAccountName $storageAccountName -StorageAccountKey $storageAccountKey $table = Get-AzureStorageTable -Name $tableName -Context $ctx

问题 I created the simple SSIS project in VS2015 with SQL Server 2012 as a targeted server, it will worked in local machine successfully without any issues. After that I have created the build definition and release definition by following this link. For this project build will be success. But release definition failed with this “##[error]Task_InternalError Exception calling ".ctor" with "1" argument(s): Failed to connect to server DNS name label.eastus.cloudapp.azure.com,1433" error message in

问题 Let's say I have these 3 Stages: Dev, QC, Prod. My requirements are: Artifacts only from specific branches(release/*) can be deployed to QC/Prod Artifacts from all branches can be deployed to Dev I can achieve what I want using Artifact filters for "After stage" triggered Releases but I need this for "Manual only". Is there a workaround that will let me control/filter which artifacts are available for deployment for specific stages/environments? Basically, I need the Azure DevOps equivalent

问题 Created a CD with few steps starting from "Azure PowerShell Task". In Azure PowerShell tasks, executing a PowerShell script file and set a value in a variable. At the end of the script I have set the variable with a value – echo "##vso[task.setvariable variable=myvariable;isSecret=false;isOutput=true;]myvalue" myvariable is the variable myvalue is the value. Based on the value of “myvariable”; downstream task will be executed or skipped. Mentioned "Custom Condition" in downstream task (Task -

问题 The below script is provided to start the Webjobs in the azure.But I am including the Json file into the Powershell script and running the Webjobs.Its good for only one environment.But I want the same script to be used for multiple environments with different Webjob names.So how can I modify this script so that I can stop and start the Webjobs in VSTS at release definition,Currently,I have 4 Webjobs for Dev Environment and I have 8 Webjobs for Int Environment with different azure

问题 My goal is to create an automated build/release pipeline that updates an Azure site every time I merge code in the GitHub project with the website. I have a website in GitHub. A VSTS GitHub build task builds it successfully. A VSTS release task (Deploy Azure App Service) deploys the site to an Azure web app successfully. I know this because the Azure App Service Editor for the Azure app shows the website files in a subdirectory under wwwroot . Because the files are deployed to a subdirectory

问题 I have a deployment slot demo that I want to update with the new application. Both Azure and VSTS confirm the release to the slot was successful. Via the Continous Delivery tab and the Release page respectively. However, when I click on the URL of the deployment slot I am taken to the old application. Any help is appreciated. 来源： https://stackoverflow.com/questions/46395014/azure-deployment-slot-not-updating-with-new-code-from-vsts

问题 I am trying to setup VSTS release management for my Azure SQL database. I am using the "Deploy Azure SQL DACPAC" task. Path to the dacpac file is setup as $(System.DefaultWorkingDirectory)\**\*.dacpac While the database updates correctly I get an error in the end that causes the task to fail. "System.Management.Automation.ParentContainsErrorRecordException: *** Could not deploy package" It looks like all the updates are applied to the database but the task still throws an error. Log below