CI/CD: A must

Nowadays the word “automation” is part of every discussion in respect of how to make our application update process easier, reliable, and more efficient.

Continuous integration (CI) refers to having a place where you can integrate and centralize your application code. Let’s call it a single repository, against which you can run processes every time something changes, such as an application build plan or quality scans, that could identify if you’re using code best practices. Even automated tests or any other process that you would like to run, to make sure you are doing things right, and nothing breaks after applying a new change. These allow developers to just concentrate on their code, and forget about whatever comes next. With a solid automated test, they can just push code to a repository as much as they need, and wait for the test result.

But we don’t want just to build and test the code, we now want to actually deploy it, and by “deploy it” we mean to run the new code wherever you or your users can get to it, that’s part of the continuous deployment process (CD).

That way the whole application update workflow gets completed, and developers are able to see the new version of an application, just by a simple code push to a repository.