Hi there AppWorks fans,
Welcome to a new installment of AppWorks tips.
This overview guide will help you get started with CI/CD on the AppWorks platform. The ‘Continuous Integration’ and ‘Continuous Delivery’ is a hot topic these days and as we are required to have a developed feature deployed from Development to Test and then from Acceptance to Production it’s almost unthinkable to do this manually.
But what is it…that CI/CD? I found a great article on infoworld.com, but in simple words: “The automation of applications on these topics: building, testing, and deploying.“
This way of automation matches exactly with the Scrum principles of this world where you want to bring small pieces to production where the DevOps principles of this world want to have that small piece to production as quick as possible a most steady, predictive and secure way!
Does it take a lot of effort and time? For sure! Does it require a lot of security bumps to take? For sure! Is it a project on itself? I would say ‘YES’, but is it worth it? Well, it depends on your demands and the willingness of the team/project…Keep in mind that it will take time in the beginning, but if you bring the effort in it will greatly improve the deployment strategy in a most valuable way.
This guide will be a series of several blog posts that will be dependent on each other and will be published each week in a row till the 3 steps are fully nailed. You are guaranteed on a great head start on CI/CD…
The required 3 steps for a best of all installation for AppWorks:
First steps for continuous deployment with the “Command Line Interface”.
Next phase for continuous deployment with “Ant-tasks”.
Last (automagically) phase on our CD/CI with “Jenkins”.
And this concludes the overview for the AppWorks CI/CD steps, I’ll give it a ‘DONE’. I will see you in the next weeks for the upcoming CI/CD posts for AppWorks. Have a great time.
