Infrastructure of Continuous Integration and Continuous Delivery
The apps we produce are generally technically advanced and they often include large amounts of source code as well as third party modules. In combination with the fast pace of mobile platform development, this means that a well-organized way of working, including reproducibility and automation, is crucial when building the code.
We have worked with the most common platforms for Continuous Integration and Continuous Delivery, such as Jenkins, Azure DevOps, Bitrise, Travis, CircleCI, TeamCity, etc. We also have vast experience in working with Fastlane and other tools that enable automation of everything from screenshots to uploading to app stores.
Natural parts of the development process are quality assurance and testing. Here the mobile platforms can be a challenge when it comes to choosing the right distribution of test versions.
What is Continuous Integration?
Continuous Integration (CI) is a method that is used in system development. Development teams frequently use version control and integrations, and CI provides consistent and automated means to build and test applications effectively.
By building and testing automatically, the development team can identify possible errors in the code and make necessary changes immediately.
What is Continuous Delivery?
Continuous Delivery (CD) is based on CI, but takes automation a step further. In CD the app is built for automatic production or acceptance tests with the purpose of enabling fast, high-quality delivery of new or updated apps.
The CD method simplifies the distribution of mobile applications. Instead of preparing for releases the developers can focus on programming. The end users can return their feedback quicker, allowing new functionality and improvements to be added more frequently.
