CI CD Pipelines With Gitlab CI

Define a GitLab CI/CD pipeline by creating a root GitLab CI YAML file and defining one or more jobs with a script that runs commands.

Learn how to ignore jobs in a GitLab CI/CD pipeline by removing a job from the configuration or prefixing its name with a dot, ensuring only the build job runs.

Skip a GitLab CI pipeline by adding CI or skip CI to the commit message, preventing automatic pipeline triggers after changes.

Define and order jobs in a GitLab CI/CD pipeline using stages. Learn to set build, test, and deploy stages, enforce sequential execution, and skip later stages on failure.

Discover how to control GitLab CI job order using the needs keyword to enforce a docker build, then test, and finally push sequence, while building cross-stage dependencies.

Learn to use before_script and after_script in GitLab CI to run commands before and after a job within a pipeline, such as creating files, simulating login, and cleaning up.

Execute a shell script in a GitLab CI build job by creating a script file, invoking it from YAML in the build stage, and using a before_script to fix permissions.

learn to save the build result as artifacts in a GitLab CI pipeline, then share build.txt with test and deploy jobs using artifacts, path, name, and expiring options.

Learn to control GitLab CI artifacts download behavior using the dependencies keyword to fetch from specific build jobs, and switch to needs with artifacts false to skip downloads.

Learn to define and use docker username, image name, and image version as global or job-level variables in a GitLab CI/CD pipeline, enabling consistent build, test, and push steps.

Learn to mask sensitive data in a GitLab CI/CD pipeline by creating project variables, setting them as masked or hidden, and using them in the docker push and deploy jobs.

Explore predefined variables in GitLab CI to build dynamic pipelines without hard coding, using pipeline, job, and job-only scopes with examples like CI_PIPELINE_ID, CI_PIPELINE_SOURCE, and CI_JOB_ID.

Learn to control GitLab CI pipeline creation with rules, using a workflow name and conditions like commit branch equals main or file existence to trigger pipelines.

Discover how to use rules at workflow and job levels to include or exclude docker jobs in a pipeline, based on image name values like webapp and webapp1.

Use pipeline schedules to trigger GitLab CI pipelines automatically on a schedule using cron syntax, with time zone, target branches or tags, variables, and manual triggering.

Specify the docker image for a GitLab CI job using the image keyword, and use the node alpine image for node and npm availability in a deploy job.