Hello.
I am building an ASP.NET web site using command line, with Visual Studio msbuild, like this:
/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true;PackageLocation=${bamboo.build.working.directory}
It works ok (it creates a deploy.cmd and a zip file in my build working directory).
In my deploy task, I also used command line and define my task like this:
msdeploy -verb:sync -source:package="ASPSample.zip" -dest:auto -setParam:kind=ProviderPath,scope=contentPath,value="Default Web Site"
In here something is going on because my Deploy keeps going for a while... I think it's some issue about the working directory, because if I use this commands in the command line (by hand) everything is working fine.
So, my question is this: what's the better solution for fixing this? (Making the deploy fetching the same directory where my build is).
Thanks.
Hi @Fr0zt if you are using deploy task on a Deployment proyect the firt step is download the artifact second one the path for "ASPSample.zip" must be absolut path you must combine the working directory + ASPSample.zip.
Cheers.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.