Which Step to Omit in the CI/CD Pipeline?
Question
A cloud native project is being worked on in which all source code and dependencies are written in Python, Ruby, and/or JavaScnpt.
A change in code triggers a notification to the CI/CD tool to run the CI/CD pipeline.
Which step should be omitted from the pipeline?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.A.
The correct step to be omitted from the CI/CD pipeline in this scenario is option C, i.e., Compile code.
In a cloud-native project, the source code and dependencies are typically written in high-level programming languages such as Python, Ruby, and JavaScript. These languages are usually interpreted or compiled at runtime, which means that the code does not need to be compiled separately before deployment.
In the context of a CI/CD pipeline, the build step is responsible for packaging the code and its dependencies into containers, which can be deployed to various environments such as staging and production. The build step is also responsible for triggering automated tests to validate the code.
The compile step, on the other hand, is typically associated with compiled languages such as C++ or Java. In these languages, the source code needs to be compiled into executable binaries before it can be run. Since the project in question uses Python, Ruby, and/or JavaScript, the compile step is not necessary and can be safely omitted from the pipeline.
In summary, in a cloud-native project that uses interpreted or just-in-time compiled languages such as Python, Ruby, and JavaScript, the compile step can be omitted from the CI/CD pipeline. The pipeline should still include steps to build containers and run automated tests to ensure that the code is properly packaged and validated.
