Continuous integration versus continuous deployment
These two words tend to appear all over current literature about proper team practice and are often confused. This is even worse with the CI/CD moniker, which refers to ways to combine them, while they are two distinct and separate activities. Let’s try to understand this.
In any development project, whether it is based on classic pro-code, written and built by developers, or based on low-code, defined by users closer to the business, the work ends up being performed in several phases.
The first phase of the project relates to the actual development of the solution. This is done using authoring environments, such as BA Studio, and the various designers accessible from it. The users using such tools are quite diverse in profile. Some are business-focused and are usually professionals in the solution domain, contributing their expertise to the solution definition. Others are developers who support this work or IT team members...