“Artifacts” are the byproducts generated via your Continuous Integration (CI) pipelines during the build process. These artifacts are compiled code (binaries) or packaged in the shape of a container image that is ready to be deployed to a server.
Welcome back to the CI/CD security series, where we continue to unravel the complexities and nuances of securing continuous integration and continuous delivery pipelines.
A deployment pipeline handles (automatically or semi-automatically) the process of configuring an environment such that a new version of an application is released.
The continuous integration security (CI) pipeline is central to the software delivery system, yet it represents a security hotspot with multiple attack vectors.
Are you struggling to grasp the intricacies of DevSecOps CI/CD pipelines? Seeking comprehensive insights on how to balance speed and security in your software development journey? Look no further.
By Gologic with the collaboration of Alexandre Couëdelo. Continuous integration (CI) and Continuous deployment (CD) are the core practices you will need to master in order to achieve a successful DevOps transformation. In this article, you will learn the CI/CD definition and what needs to be done to prepare your
By Gologic with the collaboration of Alexandre Couëdelo. Are you fuzzy about the difference between continuous integration, continuous delivery, and continuous deployment? How many times did you try to explain to someone the difference between these three DevOps practices and ended up googling it to get it right? Maybe you
Continuous integration (CI) is a key element of DevOps. Designed to automatically test the quality of the code during application updates, it facilitates and accelerates the work of the developers while ensuring better collaboration within the teams. Would you like to learn more about continuous integration in DevOps? The expert consultants from Gologic inform you
These days, DevOps is a vital practice for organizations. This movement is the result of close collaboration between the development and system operations teams. The DevOps culture continues to grow in importance. But to achieve such a performance, you need to know how to outfit yourself with the right DevOps
by Benjamin Lallement, DevOps and member of the collective Gologic. Goals Series This article series aims to explore the different tools for doing pipeline as code and deployment. The goal for each article remains the same: checkout GIT source code, compile a JAVA project with Maven, run the tests then
by Benjamin Lallement, DevOps and member of the collective Gologic. Goals Series This article series aims to explore the different tools for doing pipeline as code and deployment. The goal for each article remains the same: checkout GIT source code, compile a JAVA project with Maven, run the tests then
by Benjamin Lallement, DevOps and member of the collective Gologic. Goals Series This article series aims to explore the different tools for doing pipeline-as-code and deployment. The goal for each article remains the same: Checkout GIT source code, compile a JAVA project with Maven, run the tests then deploy the
