Deployment triggers from tags in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How do deployment triggers from tags work in CI/CD pipelines?

In a CI/CD pipeline, what is the main reason to trigger deployments based on Git tags instead of branches?

A Tags automatically merge code before deployment.

B Branches are always unstable, so tags prevent any deployment.

C Tags mark specific points like releases, so deployments happen only for those stable versions.

D Branches cannot trigger any pipeline jobs.

💡 Hint

Think about why tags are used to mark releases.

Tags are used to mark specific commits, often releases. Triggering deployments on tags ensures only stable, versioned code is deployed.

💻 Command Output

intermediate

What is the output of this Git command filtering tags?

Given the following command, what will it output?

git tag --list "v1.*"

Assume the repository has tags: v1.0, v1.1, v2.0, v1.2-beta, v1.3

A

v1.0
v1.1
v1.2-beta
v1.3

B v2.0

C

v1.0
v1.1
v1.3

D No output

💡 Hint

Check how the wildcard * works in tag filtering.

The glob pattern "v1.*" matches tags starting with 'v1.' followed by any characters: v1.0, v1.1, v1.2-beta, v1.3. v2.0 does not match.

❓ Configuration

advanced

Which GitLab CI configuration triggers deployment only on tags starting with 'release-'?

Choose the correct GitLab CI YAML snippet that triggers the deploy job only when a tag starts with 'release-'.

A

deploy:
  script: echo Deploying
  rules:
    - if: '$CI_COMMIT_TAG =~ /^release-.*/'
      when: always
    - when: never

B

deploy:
  script: echo Deploying
  only:
    - /^release-.*/

C

deploy:
  script: echo Deploying
  only:
    - tags
  except:
    - /^release-.*/

D

deploy:
  script: echo Deploying
  only:
    - branches
    - /^release-.*/

💡 Hint

Look for the syntax that supports regex matching on tags.

GitLab CI uses 'rules' with 'if' conditions to match regex on tags. Option A correctly triggers deploy only on tags starting with 'release-'.

❓ Troubleshoot

advanced

Why does deployment not trigger on new tags in this Jenkins pipeline?

A Jenkins pipeline is configured to trigger on tags, but deployments do not start when new tags are pushed. Which is the most likely cause?

A The Git repository has no tags.

B The Jenkins webhook is set to trigger only on branch pushes, not tag pushes.

C Tags are not supported in Jenkins pipelines.

D The Jenkinsfile syntax is invalid and prevents any triggers.

💡 Hint

Check webhook settings for event types.

Jenkins webhooks must be configured to listen for tag push events. If only branch pushes trigger, tags won't start deployments.

🔀 Workflow

expert

Order the steps to set up deployment triggers from Git tags in a CI/CD pipeline

Arrange the steps in the correct order to enable deployment triggers from Git tags.

A 3,2,1,4

B 3,1,2,4

C 1,2,3,4

D 1,3,2,4

💡 Hint

Think about configuring before pushing tags.

First configure the pipeline to listen for tags, then write job rules, push the tag, and finally verify deployment.

Practice

1. What is the main purpose of using tags in Git for deployment triggers?

easy

A. To merge multiple branches into one

B. To delete old branches automatically

C. To create new branches for development

D. To mark specific versions of code for deployment

Solution

1. Step 1: Understand what tags represent in Git

   Tags are labels that mark specific points in Git history, usually used for releases or versions.

2. Step 2: Connect tags to deployment triggers

   Deployment systems listen for tag pushes to know when to deploy a specific version of the code.

3. Final Answer:

   To mark specific versions of code for deployment -> Option D

4. Quick Check:

   Tags mark versions = C [OK]

Hint: Tags label versions for deployment triggers [OK]

Common Mistakes:

• Confusing tags with branches
• Thinking tags delete branches
• Assuming tags create new branches

2. Which Git command correctly creates a tag named v1.0 and pushes it to the remote repository?

easy

A. git create tag v1.0 && git push tags

B. git push tag v1.0

C. git tag v1.0 && git push origin v1.0

D. git tag create v1.0 && git push origin tags

Solution

1. Step 1: Identify the correct command to create a tag

   The command git tag v1.0 creates a tag named v1.0 locally.

2. Step 2: Identify how to push the tag to remote

   git push origin v1.0 pushes the specific tag to the remote repository.

3. Final Answer:

   git tag v1.0 && git push origin v1.0 -> Option C

4. Quick Check:

   Create tag + push tag = A [OK]

Hint: Use 'git tag' then 'git push origin tagname' [OK]

Common Mistakes:

• Using 'git push tag' which is invalid
• Trying 'git create tag' which is not a Git command
• Pushing 'tags' instead of specific tag name

3. Given this GitHub Actions snippet, what triggers the deployment workflow?

on:
  push:
    tags:
      - 'release-*'

medium

A. Any push of tags starting with 'release-'

B. Any push to branches named 'release-*'

C. Any push to any branch

D. Any push of tags named exactly 'release-*'

Solution

1. Step 1: Understand the trigger syntax

   The on.push.tags with pattern 'release-*' listens for tag pushes starting with 'release-'.

2. Step 2: Differentiate tags from branches

   This does not trigger on branches, only on tags matching the pattern.

3. Final Answer:

   Any push of tags starting with 'release-' -> Option A

4. Quick Check:

   Push tags matching pattern = A [OK]

Hint: Tags trigger with 'push.tags' and pattern [OK]

Common Mistakes:

• Confusing tags with branches in triggers
• Thinking exact tag name match is required
• Assuming all pushes trigger workflow

4. You set this in your GitHub Actions workflow:

on:
  push:
    tags:
      - 'v*'

But pushing tag release1 does NOT trigger the workflow. Why?

medium

A. The tag name does not match the pattern 'v*'

B. Tags cannot trigger workflows in GitHub Actions

C. The workflow file is missing from the repository

D. The push event only triggers on branches, not tags

Solution

1. Step 1: Analyze the tag pattern

   The pattern 'v*' matches tags starting exactly with 'v', like 'v1.0', but 'release1' starts with 'release', so it does not match.

2. Step 2: Confirm tag triggers work

   GitHub Actions supports tag push triggers, so the problem is pattern mismatch.

3. Final Answer:

   The tag name does not match the pattern 'v*' -> Option A

4. Quick Check:

   Pattern mismatch blocks trigger = B [OK]

Hint: Check tag name matches trigger pattern exactly [OK]

Common Mistakes:

• Assuming any tag triggers workflow
• Thinking tags can't trigger workflows
• Ignoring pattern matching rules

5. You want to deploy only when a tag matching deploy-* is pushed. Which GitHub Actions trigger configuration is correct?

hard

A. on:
push:
tags:
- 'release-*'

B. on:
push:
tags:
- 'deploy-*'

C. on:
tag_push:
pattern: 'deploy-*'

D. on:
push:
branches:
- 'deploy-*'

Solution

1. Step 1: Identify correct event for tag push

   The push event with tags key listens for tag pushes matching patterns.

2. Step 2: Match the pattern to desired tags

   The pattern 'deploy-*' matches tags starting with 'deploy-', exactly what is needed.

3. Step 3: Eliminate incorrect options

   on: push: branches: - 'deploy-*' listens to branches, not tags. on: tag_push: pattern: 'deploy-*' uses invalid syntax. on: push: tags: - 'release-*' matches wrong tag pattern.

4. Final Answer:

   on: push: tags: - 'deploy-*' -> Option B

5. Quick Check:

   Push tags with correct pattern = D [OK]

Hint: Use 'push.tags' with correct pattern for deployment triggers [OK]

Common Mistakes:

• Using branches instead of tags for deployment triggers
• Using invalid event names like 'tag_push'
• Mismatching tag patterns