Azure API app cannot deploy script

For continuous deployment, I can't figure out how to get the build script (Build / Advanced / MSBuild Arguments) in Team Foundation Server to work.

Yes, I used the Azure API Apps profile setting (preview) and signed into an azure account - I can post OK from there. It seems to use a password as well, which I'm not sure where this is coming from because when viewing the connection information it is hidden and it is not available in pubxml

when viewing it in the solution.

I used the following MSBuild arguments for a web app, but now if I reference the new Azure publish file it just doesn't work.

I used something like this:

/flp:verbosity="diagnostic" /p:DeployOnBuild=true /p:PublishProfile=xxx /p:AllowUntrustedCertificate=true /p:UserName="xxxx" /p:Password="xxxx" 

      

In general, there is no password for API apps, so I removed the information when testing the arguments /p

. I also made sure that the Azure SDK for VS 2013 was installed on the Team Foundation Server build, but that didn't solve anything. Please note that this solution was web application, CI and CD worked fine. Right now, if I exclude the CD, the CI works fine for the API application.

The verbose log gives me the following errors:

C: \ Program Files (X86) \ MSBuild \ Microsoft \ VisualStudio \ v12.0 \ Web \ Microsoft.Web.Publishing.targets (4350): The value for PublishProfile is "xxx" expected to find the file in 'C: \ Builds \ 4 \ Results \ yyy \ src \ ZZZ \ ZZZ \ Properties \ PublishProfiles \ xxx 'but it could not be found.

Now the files match and the file is there - I checked in the build folder. The link in the post is not related to the file extension, but it shouldn't need this part.

Anyway, I did all this with deploying web applications, and the worst thing I ever needed to do was delete the Team Foundation Server user workspaces. I also deleted all the build folders on the build machine to make sure it starts fresh. However, there is no progress on this issue.

+3


source to share


1 answer


I am using VSO BuildVNext + MSBuild to deploy my API application, here are the options for MSBuild:

msbuild.exe "[Solution_Name]" /p:DeployOnBuild=true /p:PublishProfile="[Publish_Profile_Name]" /p:UserName="[UserName]" /p:Password="[Password]" /p:platform="any cpu" /p:configuration="debug" /p:VisualStudioVersion="12.0"

      



Those username and password that I received during posting to the Azure portal (you need to go to Api App Host and download publications).

Note that it is not secure for storing passwords on the build server, so it should be used as a workaround until the Azure Powershell command is released to deploy the Api App (which can be used with a subscription ID and certificate).

0


source







All Articles