What occurs during the build stage of Continuous Integration?

During the build stage of Continuous Integration (CI), the primary focus is on compiling the code and creating build artifacts. This stage typically involves taking the source code — which may be stored in a version control system — and transforming it into a runnable application. In many modern workflows, this process may also include creating Docker images, which package the application and its dependencies in a standardized environment.

In CI, the build step ensures that the code is free of syntax errors and can compile successfully, which is essential for identifying issues early in the development process. This stage often incorporates automated scripts that handle the compilation and build processes, ensuring consistency and efficiency. The successful completion of this stage typically triggers subsequent stages such as testing, where the application is verified for functionality and performance.

While the other options do relate to the software development lifecycle, they occur in different phases. System architecture design, for example, happens earlier in the development process rather than during the build stage. Code review and testing typically follow the build, ensuring the compiled code meets quality standards. Deployment of the application occurs after successful builds and tests, moving the code into production environments. Therefore, the compilation and Docker build activities accurately represent what happens specifically during the build stage in Continuous Integration.