What is CI CD Pipeline?
CI stands for Continuous Integration and CD stands for Continuous Delivery and Continuous Deployment. You can think of it as a process which is similar to a software development lifecycle.
Now let us see how it works.
The above pipeline is a logical demonstration of how software will move along the various phases or stages in this lifecycle, before it is delivered to the customer or before it is live on production.
Why
Use Jenkin's Pipeline?
Jenkins is
an open continuous integration server which has the ability to support the
automation of software development processes. You can create multiple
automation jobs with the help of use cases, and run them as a Jenkins pipeline.
Here are the
reasons why you use should use Jenkins pipeline:
· Jenkins pipeline is implemented as a
code which allows multiple users to edit and execute the pipeline process.
· Pipelines are robust. So if your
server undergoes an unforeseen restart, the pipeline will be automatically
resumed.
· You can pause the pipeline process
and make it wait to resume until there is an input from the user.
· Jenkins Pipelines support big
projects. You can run multiple jobs, and even use pipelines in a loop.
Jenkins
Pipeline Concepts
Pipeline - The pipeline is a set of
instructions given in the form of code for continuous delivery and consists of
instructions needed for the entire build process. With pipeline, you can build,
test, and deliver the application.
Node-The machine on which Jenkins runs is
called a node. A node block is mainly used in scripted pipeline syntax.
Stage-A stage block contains a series of
steps in a pipeline. That is, the build, test, and deploy processes all come
together in a stage. Generally, a stage block is used to visualize the Jenkins
pipeline process.
Step-A step is nothing but a single task
that executes a specific process at a defined time. A pipeline involves a
series of steps.
No comments:
Post a Comment