The Agile Manifesto has had significant impact on the way software is built. It defines twelve fundamental principles, the first of which is "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software."
Helsinki, Finland is known as a center of technological innovation. Home to mobile phone pioneer Nokia and birthplace of Linux, the northernmost major city in Europe is currently one of the most vibrant hubs of technology startups in the world.
There's a lot of interest in using Stackato in conjunction with continuous integration tools, and the most popular of those tools is Jenkins CI. Until now, the only ways to deploy your applications to Cloud Foundry or Stackato from a Jenkins build were to:
In this post we will look at common steps IT organizations take when adopting cloud technologies. From starting small, and gaining expertise, to rolling out IaaS, PaaS and continuous integration. We look at one possible route you might take.
In this post, I am going to give a step-by-step introduction into how you can do continuous integration testing with Docker. I will be running the rspec test suite of the CloudFoundry project's Cloud Controller component, although the same process can be applied to any Ruby project.
Continuous delivery is not a new concept in application development and companies are looking to see how they can incorporate it. With more traditional releases, companies pack in as many features as possible and make significant changes to the software.