As you start building your new applications or perhaps maintaining your old, you soon find that automating as much part of the development lifecycle makes for faster and more robust development. We are now moving to the next phase in the “Continuous Integration” lifecycle, in which development is moving to “Continuous Deployment”. In continuous deployment, applications are deployed straight to production systems after they have been successfully built. A successful build would include steps like testing, staging on a production system etc.
This article shows you hot to take a simple application that is built on a local system and move it to the cloud (in this case using DEV@cloud SaaS and RUN@cloud PaaS). The article takes you through the following steps:
Build a local app
Local App -> manual build -> manual deploy -> Local Tomcat
Pull app from SCM -> build on local Jenkins -> continuously deploy -> Local Tomcat
Pull app from SCM -> build on local Jenkins -> continuously deploy -> RUN@cloud PaaS
Pull app from SCM -> build on DEV@cloud SaaS -> continuously deploy -> RUN@cloud PaaS
This article will help take your application (wherever it fits in the above lifecycle) and move it to the cloud. Check it out .
Stay up to date
We'll never share your email address and you can opt out at any time, we promise.