There are a lot of things that you probably are unfamiliar with when it comes to CI/CD and the operating protocols that go along with it. One of the first things that you are going to need to know is that CI/CD stands for Continuous Integration and Continuous Delivery. It can also stand for Continuous Integration and Continuous Deployment, depending on the situation.

All of these important topics will be discussed and covered so that you have a great understanding of what CI/CD means as well as how it works. You will also have the opportunity to learn about security in CI/CD pipelines and learn if there are potential security risks.

FinConDX 2021

Continuous Integration

Continuous Integration is the process where developers and contributors push code to a shared platform such as GitHub. These types of platforms are also sometimes recognized as code repositories. This process usually happens relatively often, sometimes as often as five or 20 times per day.

When the code is successfully pushed to the code repository, it is not unusual for a fully-automated testing server to check the imported code as soon as it arrives. The testing server can then provide contributors and developers with important information about the code’s performance within the testing server. The testing server can output performance attributes, checks, and other important information, as well.

This process allows developers to analyze their code and improve it with every new transfer to the code repository. Glitches can exist in code, and the process of Continuous Integration makes it possible to seamlessly find issues in programming code quickly. This process also allows for consistent code deployments to occur. 

Continuous Delivery vs. Continuous Deployment

There are a couple of minor differences between Continuous Delivery and Continuous Deployment that need to be discussed. The differences mainly have (Read more...)