continuous-deployment

I'm trying to configure Hudson so that I will be able to automatically deploy a build (a .war file) to Tomcat. The newly deployed build will then be used by someone to test the application. I've tried using the Deploy Plugin to automatically deploy the .war file, and this works. However, the job that builds the .war file will run after every scm change (whenever code is committed). With the Deploy Plugin, the .war file would be deployed to Tomcat every time a build is made. Because code is commited frequently, this will mean that the web application will be restarted frequently as well, and

After spending a couple of hours trying to understand how to make continuous deployment work in the case of an OSGi-based application , I am finally posing my first question on stackoverflow, hoping for some indications on what I might have done wrong or missed - somehow I feel being on the wrong track... This is what I want to achieve: build some bundles and install them to the maven repository (no problem here, using bnd) now having all the bundles making up my application (passing all tests and so on), I want to deploy and run the application, that is, start some OSGi framework using those

I am developing a ruby on rails website using heroku and git. What tools and features should I use to set up the following simple development process? CODE > CHECK-IN > AUTO TEST > AUTO DEPLOY I check my code into my repository (preferred option, hosted git like github) Tests are automatically run AND website is deployed in my staging heroku app If tests pass, the website is automatically deployed on my production heroku app If tests fail, I want to be notified somehow. How would you do this? We use Integrity . It is a pretty simple solution - it won't do everything under the sun, but it's

What are relational database (and schema) migration patterns on production in continuous delivery? In many traditional developments the DBA arranges a big migration script out of the many smaller scripts created in the current release cycle. But in CD the developer may want to push the change now to production, not wait to compile them with other scripts. I know on rails-migration but to me it looks more reasonable to use raw sql scripts. I've also seen tools like flyway to manage migrations but I have not read of many people using them in production. This is why I wonder what are the common

Continuous integration concept has just been integrated in my team. Assume we have an integration branch named Dev . From it derived 3 branches, one for each specific current project : Project A Project B Project C First, Teamcity is configured on a dedicated server and it goals is : Compiles and launches unit and integration tests from versioned sources from each branch including Dev Then, of course, each project branch (A,B and C) must be tested in a cloned production environment so that UAT can be carried out. But I wonder what frequency should we deploy on? Everytime a source code changes

In my team, we use Gitlab as a remote repository, so we are looking for a solution to auto deploy our apps to Heroku. We found Codeship for auto deploying apps to Heroku from Github. Any tips? Tricks? If you are not prepared to use Ruby/dpl you can deploy to Heroku as follows: Look up your Heroku API key (Account settings -> API Key on the Heroku web console) and make it available as a Gitlab secret variable e.g. HEROKU_API_KEY (Please note the values is not the same as what heroku auth:token returns...) Then add two script lines in your .gitlab-ci.yml config file at the relevant job: git

I can't make it work TFS build. It is nuget restore issue. Nuget is not restoring reference dll files. Here is belwo my build configuration. Please advise me how I can make this works. As per this blog post on Nuget's website you can use the command line you mentioned, but it has to be part of a custom target using a Build.proj file. You need to add a Build.proj and put this as the contents: <?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup> <OutDir Condition=" '$(OutDir)'=='' ">

I got a build in VSTS that are triggered on every commit in the repository. Everything works great with one exception. We do not release a new version of the nuget package on every commit. So our nuget push build step fails with http status code 409. I've configured that step so that it can continue anyway. Due to the error the build is just "partially successful". I'm using the a build badge which also states the same (without context). How can I tell VSTS to ignore 409 or just replace the existing package (on nuget.org)? You can’t ignore 409 error in VSTS build and can’t replace the existing