Continuous Delivery


Continuous Delivery means using build and test automation to minimize the delay between the time a change is ready to test, the time it is actually tested, and feedback is evaluated. At ioet we practice many development methodologies that contribute to Continuous Delivery and Continuous Deployment. These include trunk-based development, feature toggles, infrastructure-as-code, GitOps and DevSecOps. Over the years we have used many tools such Jenkins, Travis, Circle, Spinnaker, Bitrise, sinon.js, Maven, Gradle, Grunt, Ansible, and many others. Today, with most projects developed and delivered in the cloud, we are often using native-tools such as AWS CodePipeline and AWS CodeBuild, Azure Pipelines, and Google Cloud Build.