📑
docs
  • Initial page
  • Golang Shippets
    • PII Data Check
  • Docker
    • Concepts
  • NGINX Web Server Deep Dive
    • What's NGINX
  • AWS CloudFormation
    • Introduction
    • Infrastructure as Code
    • What's CloudFormation?
    • CloudFormation - Lab #1
    • CloudFormation Concepts
  • Kubernetes
    • Introduction
    • Untitled
  • Jenkins Engineer - (CJE)
    • Topics
  • Microsoft Azure - AZ-104
    • 📓Manage Azure AD Users
  • Terraform - Certified Associate
  • 🦠What is Terraform?
  • 🧬Infrastructure as Code
  • 📮Getting Started
    • 🧫Build Infrastructure
    • 🧪Change Infrastructure
    • 🧺Define Input Variables
    • 🚰Query Data with Outputs
    • 💾Store Remote State
  • 🎃Configuration Language
    • 🧼Terraform Resources
    • 💊Terraform Variables
  • 🔎Overview
    • 🗃️Configuration Syntax
  • 🎲Cheat Sheet
  • GCP - Data Engineer
    • Overview
    • Big Data and Machine Learning Fundamentals
Powered by GitBook
On this page
  • Continuous Integration (CI) / Continous Delivery (CD)
  • Workflow
  • Workflow with multiple teams

Was this helpful?

Edit on GitHub
  1. Jenkins Engineer - (CJE)

Topics

PreviousUntitledNextManage Azure AD Users

Last updated 4 years ago

Was this helpful?

Continuous Integration (CI) / Continous Delivery (CD)

  • In the integration, the area is when we start to have problems.

  • The teams (Backend, User Interface, Data) don't communicate with each other.

This is a software development practice in which members of a team integrate their work frequently, at least daily, leading to multiple integrations per day.

Workflow

Workflow with multiple teams

  • Jenkins Features and Functionality

  • Building Continuous Delivery Pipelines

  • CD as Code Best Practices

4MB
ci.gif
image
test