azure-pipelines-build-task

I'm having a strange issue where when I create a build with "Visual Studio Build" and supply the *.sln file it pretends to build all projects (I see this in the log) but when it comes to publishing artifacts there is only a few of the projects from the solution (mainly test projects and some miscellaneous projects but no the main ones) I have dependencies sorted ok as this build fine in VS2015 (I currently use WebDeploy) Has anyone seen this behavior? Since you mentioned "WebDeploy", I suspect that you are building a web app project with some other projects in the solution. The behavior you

I am using Karma and PhantomJS with Jasmine to test my AngularJS. When I run my gulp test locally it works fine, launches PhantomJS and runs all my tests, but when the tests get run on the build server it fails with the following errors: Note that I am using VSTS and using their built in cloud build system (hosted agent). Having said that its pretty much a task runner and I only use it to run gulp tasks (build, test etc) on checkin [32m13 07 2016 15:21:32.260:INFO [karma]: [39mKarma v1.1.1 server started at http://localhost:9876/ [32m13 07 2016 15:21:32.262:INFO [launcher]: [39mLaunching

I am using the "Azure Web App Deployment" build step in VSTS to publish an ASP.NET Core API to an Azure Web App: Occasionally, this step breaks with the following error: [error]Microsoft.Web.Deployment.DeploymentDetailedClientServerException: Web Deploy cannot modify the file 'MyProject.Api.exe' on the destination because it is locked by an external process. In order to allow the publish operation to succeed, you may need to either restart your application to release the lock, or use the AppOffline rule handler for .Net applications on your next publish attempt. Learn more at: http://go

I need to create around 6000 work items via my TFS extension. I use typescript and REST API in my extension. below is the code I use to create work item var ops = [ { path: "/fields/System.Title", op: "add", value: "Hello world" } ]; var options = { url: 'http://localhost:8080/tfs/DefaultCollection/Agile Git/_apis/wit/workItems/$Bug?api-version=2.2', username: 'username', password: 'password', domain: 'domain', method: 'PATCH', headers: { 'Content-Type': 'application/json-patch+json' }, body: JSON.stringify(ops) }; httpntlm.patch(options, function(err,res) { console.log("patch complete");

I need to create VSTS work items using Visual Studio Team Services Client for Node.js (vso-node-api), Please provide any samples on this? I created a simple code sample to get and create work item with it for your reference, see following section for details: /// <reference path="typings/index.d.ts" /> import * as vm from 'vso-node-api/WebApi'; import * as wa from 'vso-node-api/WorkItemTrackingApi'; import * as wi from 'vso-node-api/interfaces/WorkItemTrackingInterfaces'; import * as vss from 'vso-node-api/interfaces/Common/VSSInterfaces'; var collectionUrl = "https://xxxxxx.visualstudio.com";

I'm trying to merge the develop branch to the master branch when building with Azure Pipelines PowerShell task. But while executing the command git push , I'm getting this error: Fatal: Could not read password for ' https://OrganizationName@dev.azure.com ': terminal prompts disabled The code repository is "Azure Repos Git". git checkout -b master git config --global user.email "xxxxxxx@xxxx.xxx" git config --global user.name "xxxxx" git merge origin/develop git push origin master After referring some URLs, I've created the Personal Access Token, and modified the push command as git push https:

A project I'm working on has 2 long-standing feature branches as well as the master branch. To fully automate deployments, I'd like to create a pull request from master into those two feature branches anytime a deployment goes out from a VSTS Release. What kind of tooling in VSTS would allow me to do create pull requests as a release task? You can create the Pull Request through Pull Request REST API during the release. There is Invoke HTTP REST API task but may not good for your requirement. The simple way is that you can do it through PowerShell task : Select the phase (e.g. Run on agent)

I've defined a variable in my TFS/AzureDevops Build definition (say it's time ) and assign the value using PowerShell task within my build definition. Like, Type: Inline Script. Inline script: $date=$(Get-Date -Format g); Write-Host "##vso[task.setvariable variable=time]$date" You can refer to this similar example Now I want to get this value in my release definition pipeline. I configured this build definition as continuous deployment to my release definition. My Question is How can I get the value of time in my release definition using some other variable? Is this possible? The is no