GitLab CI/CD

This course explains what Continuous Integration/Continuous Deployment (CI/CD) pipelines are and what value they bring to the software development lifecycle. It also outlines the architecture behind GitLab's CI/CD pipelines and explains how to set up basic CI/CD pipelines in your own projects. Finally, it touches on a handful of specific CI/CD pipeline use cases, including pushing your app to a Docker Container registry and using one of GitLab's security scanners.


Estimated Effort: 3 hours

Course Format: 6 self-paced lessons

Access Duration: Up to 60 days from day of registration

Prerequisites

The target candidate should have the following knowledge:

Primary Audience

  • Development teams, quality assurance teams, release engineers
  • This course is not appropriate for students with no Git or GitLab knowledge

Learning Objectives

Upon completion of this self-paced course, learners will be able to:

  • Explain what GitLab CI/CD is and why teams use it
  • Build the GitLab CI/CD configuration file: .gitlab-ci.yml
  • Install and register a GitLab Runner
  • Learn about the available Executors used at GitLab and identify which executor(s) best support your development platforms and methodologies
  • Scope and persist variables at various levels
  • Use GitLab to build out the basics of a test, build, review, and deploy pipeline using feature/topic branching as the review mechanism
  • Utilize artifacts and dependency caching in your pipeline
  • Build and deploy images to the GitLab registry
  • Enable GitLab Security Scanning and review results

Interactivity

This self-study course employs many different learning interactions including recorded demonstrations, hands-on exercises, and other activities to ensure you retain the knowledge and skills of this course.

Technical Requirements

  • GitLab Access: Access to GitLab such as through the GitLab Demo Cloud environment is required for each attendee to participate in the hands-on activities.
  • Browser: No Internet Explorer
  • Runner Executor Needed: Shell needed to complete Hands On activities for this course. If a different executor is ready on your local machine, notify the instructor and we can plan on demoing the lab exercises.