Integración de Git con CI/CD

Welcome! In this lesson, we'll explore how Git integrates with Continuous Integration (CI) and Continuous Deployment (CD) pipelines.

CI/CD automates the process of building, testing, and deploying software. Git is at its heart, acting as the trigger for these automated workflows.

The primary way Git communicates with CI/CD tools is through webhooks.

• A webhook is an automated HTTP POST request.
• Git hosting services (like GitHub, GitLab, Bitbucket) send these requests.
• They notify your CI/CD system about events, such as a new code push or a pull request.

Setting up a webhook is usually straightforward:

1. Navigate to your repository's settings on your Git hosting service.
2. Find the 'Webhooks' or 'Integrations' section.
3. Add a new webhook, providing the URL of your CI/CD tool.
4. Select which Git events (e.g., push, pull request) should trigger the webhook.

Once a webhook triggers, your CI/CD pipeline kicks into action. Here's a typical flow:

• Trigger: A Git event (e.g., a git push).
• Build: The code is compiled, dependencies are installed, and build artifacts are created.
• Test: Automated tests (unit, integration, end-to-end) are run against the built code.
• Deploy: If tests pass, the artifacts are deployed to a target environment (e.g., staging, production).

Let's look at a basic GitHub Actions workflow file. This YAML configuration defines a simple pipeline that runs on every push to the main branch.

It checks out the code and then prints a message.

You can optimize CI/CD by triggering pipelines only for specific branches or changes.

For example, you might only want to run a full deployment pipeline when changes are pushed to main or develop, saving resources on feature branches.

Many CI/CD tools allow you to specify branch patterns, paths, or commit types for triggers.

Sometimes, you might make a small commit (e.g., fixing a typo) that doesn't require a full CI/CD run.

Most CI/CD platforms support special keywords in commit messages to skip a pipeline run. Common examples include:

• [skip ci]
• [ci skip]
• [no ci]

Adding this to your commit message prevents unnecessary builds.

CI/CD tools can report the status of builds and tests directly back to your Git hosting service.

This allows you to set up protected branches. With protected branches, you can enforce rules like:

• Requiring all CI/CD status checks to pass before a merge.
• Requiring a minimum number of approving code reviews.

This ensures only high-quality, tested code lands in critical branches.

The 'Continuous Deployment' part of CI/CD often means that after successful builds and tests, the pipeline automatically deploys your application.

This can involve:

• Updating cloud services (e.g., AWS, Azure).
• Deploying to Kubernetes clusters.
• Pushing new packages to artifact repositories.

Git ensures that the deployed version always reflects the latest approved code.

Let's quickly check your understanding of how Git notifies CI/CD tools.

You've learned how Git is fundamental to CI/CD workflows! We covered:

• Git events triggering pipelines via webhooks.
• The typical stages of a CI/CD pipeline.
• Configuring basic workflows and optimizing triggers.
• Using commit messages to skip CI/CD runs.
• Leveraging status checks and protected branches for quality.

Git makes automation possible, ensuring efficient and reliable software delivery.