Why Git integrates with CI/CD - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to show the Git command that triggers a CI/CD pipeline on a new commit.

Git

git [1]

Drag options to blanks, or click blank then click option'

Acommit

Bclone

Cpush

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git commit' only saves changes locally and does not trigger CI/CD.

Using 'git clone' downloads a repository but does not trigger CI/CD.

The git push command sends your committed changes to a remote repository, which often triggers the CI/CD pipeline to start automated testing and deployment.

2fill in blank

medium

Complete the sentence to explain why Git is used with CI/CD: "Git helps by {{BLANK_1}} code changes so CI/CD can test and deploy them."

Git

"Git helps by [1] code changes so CI/CD can test and deploy them."

Drag options to blanks, or click blank then click option'

Atracking

Bignoring

Chiding

Ddeleting

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking Git hides or deletes changes, which is incorrect.

Ignoring changes would prevent CI/CD from working.

Git tracks code changes, which allows CI/CD systems to detect updates and run automated tests and deployments.

3fill in blank

hard

Fix the error in the Git command that triggers CI/CD after code changes: "git {{BLANK_1}} origin main"

Git

git [1] origin main

Drag options to blanks, or click blank then click option'

Apull

Bpush

Cfetch

Dmerge

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git pull' downloads changes but does not trigger CI/CD.

Using 'git fetch' only updates remote tracking branches.

The correct command to send your local changes to the remote repository and trigger CI/CD is git push origin main.

4fill in blank

hard

Fill both blanks to complete the Git hook script that triggers CI/CD on push: "#!/bin/sh\n{{BLANK_1}} -u origin main\n{{BLANK_2}}"

Git

#!/bin/sh
[1] -u origin main
[2]

Drag options to blanks, or click blank then click option'

Agit push

Bexit 0

Cgit commit

Decho 'CI/CD triggered'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git commit' instead of 'git push' in the hook.

Not exiting the script properly can cause errors.

The script pushes changes to the remote with git push -u origin main and then exits successfully with exit 0, which is standard for Git hooks.

5fill in blank

hard

Fill all three blanks to create a GitHub Actions workflow step that runs CI/CD on push: "on: push\njobs:\n build:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v2\n - name: Run tests\n run: {{BLANK_1}} {{BLANK_2}} {{BLANK_3}}"

Git

on: push
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Run tests
        run: [1] [2] [3]

Drag options to blanks, or click blank then click option'

Apython3

B-m

Cunittest

Dnpm

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'npm' here would be wrong for Python tests.

Missing the '-m' flag causes the module not to run.

This step runs Python unit tests using python3 -m unittest, which is a common way to run tests in CI/CD pipelines.

Practice

1. Why is Git commonly integrated with CI/CD pipelines in software development?

easy

A. To replace the need for writing code documentation

B. To manually approve every code change before merging

C. To store large binary files efficiently

D. To automatically test and deploy code when changes are made

Solution

1. Step 1: Understand Git's role in code changes

   Git tracks code changes and allows developers to push updates to a shared repository.

2. Step 2: Connect Git with CI/CD automation

   Integrating Git with CI/CD triggers automated tests and deployments when code is pushed, speeding up delivery and catching errors early.

3. Final Answer:

   To automatically test and deploy code when changes are made -> Option D

4. Quick Check:

   Git + CI/CD = Auto test & deploy [OK]

Hint: Git triggers CI/CD to automate tests and deployment [OK]

Common Mistakes:

• Thinking Git replaces documentation
• Believing Git integration means manual approvals
• Confusing Git with file storage tools

2. Which Git event commonly triggers a CI/CD pipeline automatically?

easy

A. git clone

B. git push

C. git status

D. git branch

Solution

1. Step 1: Identify Git commands related to repository changes

   Commands like git push send local commits to the remote repository.

2. Step 2: Understand CI/CD triggers

   CI/CD pipelines usually start when new code is pushed to the repository, so git push triggers the pipeline.

3. Final Answer:

   git push -> Option B

4. Quick Check:

   Push triggers CI/CD [OK]

Hint: CI/CD pipelines start on git push events [OK]

Common Mistakes:

• Confusing git clone with triggering pipelines
• Thinking git status triggers CI/CD
• Assuming git branch triggers pipelines

3. Given this Git commit and CI/CD setup, what happens after running git push origin main?

1. Developer commits code locally
2. Runs git push origin main
3. CI/CD pipeline is configured to run tests on push to main branch

medium

A. The local commit is deleted

B. The code is deployed without any tests

C. The pipeline runs tests automatically on the new code

D. Nothing happens until manual approval

Solution

1. Step 1: Understand the push triggers pipeline

   Pushing code to the main branch triggers the CI/CD pipeline configured to run tests on that branch.

2. Step 2: Identify pipeline behavior

   The pipeline runs automated tests on the new code before deployment to catch errors early.

3. Final Answer:

   The pipeline runs tests automatically on the new code -> Option C

4. Quick Check:

   Push to main triggers tests [OK]

Hint: Push to main runs tests automatically [OK]

Common Mistakes:

• Assuming deployment happens without tests
• Thinking manual approval is always needed
• Believing local commits affect remote pipeline

4. A developer notices the CI/CD pipeline does not start after pushing code. Which Git-related issue could cause this?

medium

A. Pushing to a branch not monitored by the pipeline

B. Using git commit without git push

C. Running git status before pushing

D. Deleting the local repository

Solution

1. Step 1: Check branch monitored by CI/CD

   CI/CD pipelines usually watch specific branches like main or develop. Pushing to an unmonitored branch won't trigger the pipeline.

2. Step 2: Understand push vs commit

   While committing saves changes locally, only pushing sends changes to remote and triggers CI/CD. But here, the problem is the branch.

3. Final Answer:

   Pushing to a branch not monitored by the pipeline -> Option A

4. Quick Check:

   Branch must be monitored to trigger CI/CD [OK]

Hint: Pipeline triggers only on monitored branches [OK]

Common Mistakes:

• Confusing commit with push
• Thinking git status triggers pipeline
• Assuming deleting local repo affects remote pipeline

5. How does integrating Git with CI/CD pipelines improve software delivery in a team environment?

hard

A. By automatically running tests and deployments on code changes, reducing errors and speeding releases

B. By requiring developers to manually test and deploy every change

C. By storing all code versions in a single large file

D. By preventing any code changes without manager approval

Solution

1. Step 1: Understand automation benefits

   Git integration with CI/CD automates testing and deployment, catching errors early and reducing manual work.

2. Step 2: Recognize impact on team delivery

   This automation helps teams release software faster and with higher quality by ensuring code is tested before deployment.

3. Final Answer:

   By automatically running tests and deployments on code changes, reducing errors and speeding releases -> Option A

4. Quick Check:

   Automation improves delivery speed and quality [OK]

Hint: Automation with Git + CI/CD speeds delivery and reduces errors [OK]

Common Mistakes:

• Thinking manual testing is required every time
• Confusing Git with file storage
• Assuming all changes need manager approval