Scribd
Upload
10 views10 pages

CI - CD Pipelines Flow

Uploaded by

kpreddy13011997
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views10 pages

CI - CD Pipelines Flow

Uploaded by

kpreddy13011997
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Master the

CI/CD Pipeline
Flow
Land Your Next

Dev Job
Code Repository: Developers commit code
changes to the repository.

Build: The CI system automatically builds the


code into a deployable artifact (e.g., Docker
image, JAR file).

Pre-deployment Tests: Automated tests (unit


tests, integration tests, etc.) are executed on the
build to ensure code quality and functionality.

Decision: 

Tests Failed: - Report the test failures and stop

the pipeline. Developers need to fix the issues

and commit new code. - Go back to Step 2: Build.

- **Tests Passed:** 

- Proceed to **Deploy to Staging**.

www.learnbay.co
Deploy to Staging: The build is deployed to a
staging environment, which mimics the
production environment.

Staging Tests: Automated tests (e.g., end-to-end


tests, smoke tests) are executed in the staging
environment to ensure the application works as
expected.

Decision:

Tests Failed: - Report the test failures. Developers


need to fix the issues and commit new code. - Go
back to Step 2: Build.

- **Tests Passed:** 

- Proceed to **Deploy to Production**.

Deploy to Production: The build is deployed to


the production environment.

Monitor and Logging: The application's


performance and health are monitored in
production. Logs are collected and analyzed for
any issues.
Land Your Next Dev Job:

Master the CI/CD Pipeline Flow

In today's fast-paced development world, understanding

CI/CD pipelines is crucial. This carousel will guide you

through the key steps involved in this essential process.


Key Steps in the CI/CD Pipeline
Code Repository: Developers commit code changes
to a central repository like Git.

Build: The CI system automatically builds the code


into a deployable artifact, such as a Docker image.

Pre-deployment Tests: Automated tests (unit tests,


integration tests) are executed to ensure code quality
and catch issues early on.
Deploying and Testing

Deploy to Staging: The built code is deployed to a


staging environment, which mirrors the production
environment.

Staging Tests: More comprehensive tests (e.g., end-


to-end tests, smoke tests) are performed in the
staging environment to validate the application's
behavior in a production-like setting.

Deploy to Production: If all tests pass in the staging


environment, the code is finally deployed to the
production environment for users to access.
Monitoring and Maintenance
Monitor & Logging: The application's performance
and health are continuously monitored in production.
Logs are collected and analyzed to identify and
address any issues that may arise.
Boost Your Career Prospects
Understanding CI/CD principles demonstrates a strong
grasp of modern development practices. It showcases
your ability to work efficiently, collaborate effectively,
and deliver high-quality software.
Take Your Skills
to the Next
Level!
visit
www.learnbay.co

EXPLORE OUR COURSES

DATA SCIENCE & AI SOFTWARE DEVELOPMENT


PROGRAMS PROGRAMS

Get Certification from :


IIT

Guwahati

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy