Deployment triggers from tags in Git - Step-by-Step Execution

Process Flow - Deployment triggers from tags

Create or push a Git tag

↓

Git detects new tag event

↓

CI/CD system listens for tag events

↓

Trigger deployment pipeline

↓

Deploy application based on tag version

↓

Notify success or failure

This flow shows how pushing a Git tag can trigger a deployment pipeline automatically.

Execution Sample

Git

git tag v1.0.0

git push origin v1.0.0

Create a tag named v1.0.0 locally and push it to the remote repository to trigger deployment.

Process Table

Step	Action	Event Detected	Pipeline Triggered	Deployment Status
1	Create tag v1.0.0 locally	No	No	No
2	Push tag v1.0.0 to origin	Yes (tag push)	Yes	Started
3	CI/CD pipeline runs deployment	N/A	N/A	Success
4	Notify deployment result	N/A	N/A	Completed

💡 Deployment completes successfully after pipeline triggered by tag push event.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Tag Exists on Local	No	Yes (v1.0.0)	Yes (v1.0.0)	Yes (v1.0.0)	Yes (v1.0.0)
Tag Exists on Remote	No	No	Yes (v1.0.0)	Yes (v1.0.0)	Yes (v1.0.0)
Pipeline Triggered	No	No	Yes	Yes	Yes
Deployment Status	Not started	Not started	Started	Success	Completed

Key Moments - 3 Insights

Why does deployment not start when the tag is created locally?

Deployment triggers only when the tag is pushed to the remote repository, as shown in step 2 of the execution table.

What event causes the CI/CD pipeline to start?

The pipeline starts on detecting a tag push event to the remote repository, as indicated in step 2.

Can deployment happen without pushing the tag to remote?

No, deployment triggers rely on remote events; local tags alone do not trigger pipelines.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the pipeline get triggered?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Check the 'Pipeline Triggered' column in the execution table.

According to the variable tracker, when does the tag appear on the remote repository?

A After Step 3

B After Step 1

C After Step 2

D At Start

💡 Hint

Look at the 'Tag Exists on Remote' row in the variable tracker.

If you skip pushing the tag, what happens to the deployment status?

A Deployment starts immediately

B Deployment status remains 'Not started'

C Deployment fails

D Deployment status shows 'Success'

💡 Hint

Refer to the key moment about local tag creation without pushing.

Concept Snapshot

Deployment triggers from tags:
- Create a tag locally with 'git tag <name>'.
- Push the tag to remote with 'git push origin <tag>'.
- CI/CD listens for tag push events.
- On tag push, deployment pipeline runs automatically.
- Deployment status updates after pipeline completes.

Full Transcript

This visual execution shows how deployment triggers from Git tags work. First, a tag is created locally but this alone does not trigger deployment. When the tag is pushed to the remote repository, the CI/CD system detects this event and triggers the deployment pipeline. The pipeline runs and deploys the application version matching the tag. Finally, the deployment status updates to success and notifications are sent. Variables like tag existence on local and remote, pipeline trigger state, and deployment status change step-by-step as shown in the tables. Key moments clarify that only pushing tags triggers deployment, not local creation alone.