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.