continuous-deployment

I'm getting this problem using VSTS continuous deployment to azure Web Deploy cannot modify the file 'XXX' on the destination because it is locked by an external process the solution provided in this thread is to manually restart my app in azure, however he's not using VSTS and the question was asked 2 years ago, is this issue fixed on the current VSTS and if so, I would like to know how because I'm having the same problem as the link referenced above. Thanks Eddie Chen - MSFT You can use "EnableMSDeployAppOffline" feature to set your app offline before deployment by following the instruction

I have created an Azure Web Site and connected it to Visual Studio Online, and this automatically set up a continuous deployment build (as per this page ). Initially this worked for a solution with one project, but now I have added a Web API project as a back end. This is named such that it is the first of the two projects alphabetically , and so now it is the only project that gets built and deployed whenever files are checked in. Which leads to my question: How can I modify the default continuous deployment build to deploy both applications? I'm sure it must be a fairly simple change to

My build in Visual Studio Online tries to deploy my Azure web site via Kudu . The script works fine, and deployment goes through, but VSO treats git output as errors for some reason, and declares the whole build failed. Take a look at the screenshot below. Some details: This is a "new scripted" build, not a XAML-defined one. Build definition has just one step, which executes a PowerShell script, which runs F# FAKE (not sure if this is relevant). When I run the same script on my local machine, I don't see any "strange" output, including the [K at the end of each line. After running on my local,

I am using Visual Studio Online to deploy my project continuously after the CI build pass. However I have to use a publish profile to build the production web.config transform so that the deployed website will be using the production DB instead of dev DB. I have followed Scott Hanselman's blog post to add the MSBuild arguments in the CI build definition. My arguments are like this: /p:DeployOnBuild=true /p:PublishProfile=[publish profile name] /p:AllowUntrustedCertificate=true /p:UserName=[credentials obtained from Azure Website portal] /p:Password=[from the portal as well] It seems working,

Is it possible to trigger a Hudson/Jenkins build only when a certain string appears in a commit-message? For instance, I want to trigger a build that rolls out my application to the dev environment by writing a commit message like: MYPROJECT-123 Fixed NPE in MyClass.java #deploy:DEV The general idea is described in this great talk on Continuos Deployment but I couldn't find any information on how to do this in Hudson. I would prefer to have this behavior in Hudson itself and not in an external system like commit-hooks or web-hooks. I don't know of an out of the box way you can parse the SCM

I am trying to get travis-ci to run a custom deploy script that uses awscli to push a deployment up to my staging server. In my .travis.yml file I have this: before_deploy: - 'curl "https://s3.amazonaws.com/aws-cli/awscli-bundle.zip" -o "awscli-bundle.zip"' - 'unzip awscli-bundle.zip' - './awscli-bundle/install -b ~/bin/aws' - 'export PATH=~/bin:$PATH' - 'aws configure' And I have set up the following environment variables: AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION with their correct values in the travis-ci web interface. However when the aws configure runs, it stops and waits