As we are using Bamboo for CI-CD, we have build the artifact using Visual studio agent and the artifact also generated now we want to publish it on IIS server.
Any help on this.
My solution for this was to create a publishing profile in my visual studio project/website.
Then, in bamboo I created a build-plan that creates a shared artifact, that can be consumed in a deployment project.
The trick with the deployment-project it seems is to specify Visual Studio version in parameters also.
So, in the deployment-project MSBuild-task I point to the .csproj file for the web-project in the shared artifact and set up parameters like this (under options);
/p:Configuration=Release /p:DeployOnBuild=True /p:PublishProfile="nameofpublishingprofile" /p:ProfileTransformWebConfigEnabled=False /p:Password="ftppassword" /p:AllowUntrustedCertificate=true /p:UserName=ftpusername /p:VisualStudioVersion=14.0
Without specifying visualstudioversion it seems to choke on targets.
I'm not sure if you need to specify username and password if it is allready set up in the publishingprofile, but the above parameters seems to make it work.
Also; If there are files included in the solution that is not committed or ignored in bitbucket, the deployment will fail, since it cannot copy the file.
Hope you make it work :)
Any luck on this? I am creating articfact through a build in bamboo and all is well.. I have a deployment project set up in bamboo as well that consumes this package and deploys it with msbuild, using a publishingprofile in the artifacty/project.
However, the artifact contains a visual studio project with the complete website, including views, css etc.. The deployment-project just seems to deploy the .bin files and nothing else.. It completely ignores the changes to views and doesn't deploy those. What am I missing?