azure-pipelines

问题 I've released a bunch of Docker apps on Azure App Services in the past, but for some reason, after creating a new build and release pipeline in Azure DevOps, my Docker containers won't run in an Azure App Service. These particular containers are on the Linux flavor. Switching between various Docker images, any built with the old pipeline work, but ones built with the new pipeline do not. When I copy-paste the exact command from the App Service's log file into my local command line, it works

问题 I have a visual studio team services build setup. I have 2 steps so far. Visual Studio Build - this works beautifully Copy files - this works depending on where I set the target path too. Now I need the outputted files to be deployed to our application. There are multiple tasks to use: copy files, copy and publish build artifacts, publish build artifacts, etc. I decided on copy files because it seemed the most straight forward, and after all, I just need to copy files. :) My issue is that if

问题 I am Building C# Application using Visual Studio Build In Azure Pipeline. My solution Contains multiple project (ManagerWeb & WebAPI). I want to Publish Two Separate Artifact ManagerWeb & WebAPI respectively. All the required File's are present in Build.ArtifactStagingDirectory . How I can specify a pattern using which I can get Two Separate Artifact ? Example All the File name with WebAPI in 1st Artifact & ManagerWeb in another. The File name from ArtifactStaging Directory are as Below

问题 Im setting up a release pipeline task to transform my app.config using variables to replace several connectionstring values. These properties are not in the node, but rather in a seperate node. Does the File Transform task work only with settings in the node or anywhere in the file? The attribute on the connectionstring properties are name and "connectionString", eg. <connectionStrings> <add name="conn1" connectionString="conn 1 string"/> </connectionStrings> What do I put in the value field

问题 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 created a Docker Host Service Connection in Azure Devops Services. But I can't see how I can refer to that service connection from the azure-pipeline.yml file. Can someone help? 回答1: How to use Docker Host Service Connection in Azure Pipelines I am afraid that this should be a legacy of a unpublished task Docker Integration. Because this task is in an unpublished state at this time, we cannot use it. If necessary, it is recommended to use docker and Docker Compose tasks. That the reason why

问题 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 using Azure Pipeline to build and run test for iOS code. Those steps works fine. How to display the build status in bitbucket? I could find a script: #!/usr/bin/env python import os import requests # Use environment variables that your CI server provides to the key, name, # and url parameters, as well as commit hash. (The values below are used by # Jenkins.) data = { 'key': os.getenv('BUILD_ID'), 'state': 'SUCCESSFUL', # or 'FAILED' for a script that runs when the build fails 'name': os

问题 I have a build and release pipeline in Azure DevOps. The build has archive and publish steps. And then the release picks up the archives to deploy them. The build has a parameter where I specify the environment, changing some of the build command arguments. So the build can easily create archives for different environments. I then have a release for each environment, but I cannot tell which archive belongs to which environment because the version is determined by today's date plus a number.

问题 I have a build and release pipeline in Azure DevOps. The build has archive and publish steps. And then the release picks up the archives to deploy them. The build has a parameter where I specify the environment, changing some of the build command arguments. So the build can easily create archives for different environments. I then have a release for each environment, but I cannot tell which archive belongs to which environment because the version is determined by today's date plus a number.