Home Lab Access & Prerequisites Navigating GitLab Projects and CI/CD in Your DevSecOps Lab

Navigating GitLab Projects and CI/CD in Your DevSecOps Lab

Last updated on Feb 09, 2026

Navigating GitLab Projects and CI/CD in Your DevSecOps Lab

Whether you’re new to GitLab or transitioning from an older version, understanding where to find your projects, how to interpret CI/CD status, and what branch conventions to follow can make your lab experience smoother and more productive. This guide walks you through the most common hurdles you might encounter in a DevSecOps lab environment, complete with step‑by‑step instructions, practical examples, and a handy FAQ.

Table of Contents

  1. Finding Your GitLab Project

  2. Viewing CI/CD Status in GitLab 17.x

  3. Branch Naming: main vs. master

  4. Lab Layout: Instructions vs. Lab Environment

  5. Tips for a Seamless Lab Experience

  6. Common Questions (FAQ)

Finding Your GitLab Project

Why the UI changed

  • GitLab 16.x displayed all of your projects automatically on the dashboard right after login.

  • GitLab 17.x introduced a cleaner home page; you now need to click Explore projects to see the full list.

Step‑by‑step guide (GitLab 17.x)

  1. Log in to your GitLab instance.

  2. In the left‑hand navigation bar, locate the Explore icon (a compass).

  3. Click Explore → Projects.

  4. Use the search bar or filters (e.g., Owned by me, Group, Visibility) to locate the lab project you need.

Pro tip: Bookmark the “Explore projects” URL (e.g., https://gitlab.example.com/explore/projects) for quick access in future sessions.

Viewing CI/CD Status in GitLab 17.x

What changed?

In earlier releases, the CI/CD pipeline’s pass/fail badge appeared directly on the project cards. GitLab 17.x now shows the status only after you open the project.

How to see the pipeline result

  1. After locating your project (see the previous section), click the project name to open its overview page.

  2. The CI/CD widget near the top will display the latest pipeline status:

    • ✅ Passed – all jobs succeeded.

    • ❌ Failed – one or more jobs did not complete successfully.

  3. Click the pipeline badge to drill down into individual job logs if you need to troubleshoot.

Example scenario

You just pushed a change to the repository and wonder if the security scan passed.

  • Open the project → CI/CD widget shows ❌ Failed.

  • Click the failed pipeline → identify the Static Application Security Testing (SAST) job that flagged an issue.

  • Fix the code, push again, and verify the status turns green.

Branch Naming: main vs. master

Historical context

  • GitHub switched its default branch name from master to main in 2020 to promote inclusive terminology.

  • Many organizations, including our DevSecOps labs, have adopted the same convention.

Can you still use master?

  • Yes. The lab pipelines are configured to run on any branch you push, including master.

  • Recommendation: Use main for new repositories to stay aligned with industry standards and avoid confusion when collaborating with external teams.

Quick command to rename a local branch

# Rename local master to main
git branch -m master main

# Push the renamed branch and set upstream
git push -u origin main

# (Optional) Delete the old remote branch
git push origin --delete master

Lab Layout: Instructions vs. Lab Environment

Current limitation

The learning platform does not support splitting the lab instructions and the interactive environment across two separate screens or windows.

Work‑around suggestions

  • Dual‑monitor setup: Open the instructions in a browser tab on one monitor and the lab environment (e.g., VS Code, terminal, or GitLab UI) on the other.

  • Browser windows: Drag the instruction tab to the left side of the screen and the lab tab to the right, using the OS’s split‑view feature.

While not a native feature, these approaches give you a quasi‑split view that can improve focus and reduce context switching.

Tips for a Seamless Lab Experience

Tip Why it helps
Bookmark key pages (Explore projects, pipeline view) Saves time navigating between sections.
Enable browser notifications for GitLab Instantly know when a pipeline finishes.
Use a consistent branch name (main) Aligns with the lab’s documentation and avoids mismatched references.
Keep a terminal session open Quickly run git status or git log without leaving the lab UI.
Take screenshots of error messages Helpful for real agent or instructor feedback.

Common Questions (FAQ)

Q1: I can’t find my project after logging in.
A: In GitLab 17.x you must click Explore → Projects. If you still don’t see it, verify you’re logged into the correct group or ask the lab admin to confirm your access rights.

Q2: The CI/CD badge still shows “No pipeline” after opening the project.
A: This usually means a pipeline hasn’t been triggered yet. Push a commit to any branch (e.g., git push origin main) to start the pipeline.

Q3: My lab instructions mention the master branch, but my repo only has main.
A: The lab works with either branch. Update the instruction step to reference main or rename your branch using the commands above.

Q4: Can I view the instructions on a tablet while working on the lab on a laptop?
A: Yes—simply open the instruction URL on a separate device. The platform does not enforce a single‑screen view.

Q5: I see a red “Failed” badge but the job logs are empty.
A: Refresh the pipeline page; sometimes logs load with a slight delay. If they remain empty, check the runner’s health status in Admin → Runners (or ask support).

Bottom Line

Navigating GitLab’s updated UI, interpreting CI/CD status, and adhering to modern branch naming conventions are essential skills for any DevSecOps practitioner. By following the steps and tips outlined above, you’ll spend less time hunting for information and more time mastering the security‑focused workflows that the lab is designed to teach. Happy coding!