azure-devops

问题 yaml PowerShell task looks something like this: - task: PowerShell@2 displayName: 'test' inputs: targetType: filePath filePath: '$(Agent.BuildDirectory)\$(artifactName)\testpath\testscript.ps1' arguments: '-parameterFilePath $(Agent.BuildDirectory)\$(artifactName)\mainfolder\params.json -appSecurePassword (convertTo-SecureString $(appPassword) -AsPlainText -Force) -vmSecurePassword (convertTo-SecureString $(vmPassword) -AsPlainText -Force)' However, I get this error: 2020-06-09T12:54:59

问题 I'm building a multi-stage pipeline, and I'm using a lot of templates as the deploy jobs, tasks, and stages for each environment has a lot of shared logic. So on the stage I'm setting a environmentName variable, then using that in each of the jobs: - stage: StageReleaseProd displayName: Stage Release (Prod) variables: environmentName: 'prod' jobs: - deployment: DeployWebApp displayName: Deploy Wep App pool: vmImage: $(vmImage) environment: $(environmentName) strategy: runOnce: deploy: steps:

问题 I have a variable called some_var in an Azure DevOps release pipeline. I'd like to set the default at release time. But I want to set it programmatically based on the contents of a file in the artifact drop folder. But I still want the user to be able to overwrite the dynamically set value at the time they're creating the release. So the end-user behavior would be that they (1) navigate to the Release and (2) click "Create New". The dialog comes up with the some_var variable already set to a

问题 I have an Azure DevOps Pipeline which pulls from a repository and builds a Visual Studio web project. This is then published to an App Service. I have several sensitive configuration files which are not included in the repository (or the VS project) and are stored as 'Secure Files' within the Azure DevOps system. I need to include these files in the 'Config/Secure' folder for the package that gets published (within the zip file). I can download them, but no matter what I try, I cannot get

问题 As a centralized azure devops team in my org , we want to ensure that code of certain technology type built using standard extended yaml template. Thanks to the "Extend" feature and recently introduced template check at environment level , we are now able to verify developers yamls if they are extending our standard yamls or not. But this check only runs after build stage. Can we somehow evaluate this before build stage? 回答1: Can we somehow evaluate this before build stage? I'm afraid, no, it

问题 could someone help me please: I am using Azure cli behind proxy and I have fiddler running. I am running following commands and setup to login into my azure account, SET ADAL_PYTHON_NO_SSL_VERIFY=1 SET AZURE_CLI_DISABLE_CONNECTION_VERIFICATION=1 az login --tenant <company domain> It works well and gives me the list of subscriptions associated with my account.But, I need to install Azure-devops extension and when i run: az extension add --name azure-devops I am getting error: cli.azure.cli

问题 I opened an excel file generated with TFS Office Integration (TFS 2017 update 1 on premises). I obtained this error "TF84021 - Could not create the work item list". How resolve this error? What caused this error? 回答1: How resolve error “TF84021 - Could not create the work item list” with TFS Office Integration? To use that extension, you need make sure you have installed the requires Microsoft Excel and one of the following clients to be installed: Visual Studio 2017 or later Team Foundation

问题 I am trying to use a pre-deployment gate(Query Azure Monitor alerts) in release pipeline. Also I am trying to fetch the alerts since last 30d, but the api version 2018-05-05 is not populating the result. But if I have the api version to 2019-03-01 all alerts are shown. Problem is the Query Azure Monitor alerts gate is using the api version 2018-05-05, Is there any way to change this inside gate and use the new api version 2019-03-01 ? Please let me know if there is any other way to get the

问题 I am using azure devops to host an authenticated NPM feed. I would like to generate a token to access that feed using the CLI. The instructions on azure devops involve going through the web interface to generate a personal access token (PAT), then base64-ing that token, and adding it to the .npmrc. If I do that, I'm able to run npm install against that feed without issue. In the CLI, I've tried using az account get-access-token , grabbing that token, and encoding it. But that seems to fail,

问题 My requirement is I want to integrate my Bitbucket repo with the Azure DevOps CI server so that as soon as I push code in the bitbucket repo my pipeline should trigger in the Azure DevOps CI server for that I have created a webhook in the Bitbucket repo. I have added the Azure DevOps CI server URL in the URL section and added secret in a secret section of the webhook of Bitbucket. the secret is personal access token generated in Azure DevOps Server. But while creating a webhook I am getting