# This file is a template, and might need editing before it works on your project.
# This is a sample GitLab CI/CD configuration file that should run without any modifications.
# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
# it uses echo commands to simulate the pipeline execution.
#
# A pipeline is composed of independent jobs that run scripts, grouped into stages.
# Stages run in sequential order, but jobs within stages run in parallel.
#
# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages
#
# You can copy and paste this template into a new `.gitlab-ci.yml` file.
# You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword.
#
# To contribute improvements to CI/CD templates, please follow the Development guide at:
# https://docs.gitlab.com/ee/development/cicd/templates.html
# This specific template is located at:
# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml

	# This file is a template, and might need editing before it works on your project.
	# This is a sample GitLab CI/CD configuration file that should run without any modifications.
	# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
	# it uses echo commands to simulate the pipeline execution.
	#
	# A pipeline is composed of independent jobs that run scripts, grouped into stages.
	# Stages run in sequential order, but jobs within stages run in parallel.
	#
	# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages
	#
	# You can copy and paste this template into a new `.gitlab-ci.yml` file.
	# You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword.
	#
	# To contribute improvements to CI/CD templates, please follow the Development guide at:
	# https://docs.gitlab.com/ee/development/cicd/templates.html
	# This specific template is located at:
	# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml
	stages: # List of stages for jobs, and their order of execution
	- build
	- test
	- deploy
	build-job: # This job runs in the build stage, which runs first.
	stage: build
	script:
	- echo "Compiling the code..."
	- echo "Compile complete."
	unit-test-job: # This job runs in the test stage.
	stage: test # It only starts when the job in the build stage completes successfully.
	script:
	- echo "Running unit tests... This will take about 60 seconds."
	- sleep 60
	- echo "Code coverage is 90%"
	lint-test-job: # This job also runs in the test stage.
	stage: test # It can run at the same time as unit-test-job (in parallel).
	script:
	- echo "Linting code... This will take about 10 seconds."
	- sleep 10
	- echo "No lint issues found."
	deploy-job: # This job runs in the deploy stage.
	stage: deploy # It only runs when *both* jobs in the test stage complete successfully.
	environment: production
	script:
	- echo "Deploying application..."
	- echo "Application successfully deployed."

view raw .gitlab-ci.yml hosted with by GitHub

.gitlab-ci.yml file to run with Docker runner

image: busybox:latest

before_script:
  - echo "Before script section"
  - echo "For example you might run an update here or install a build dependency"
  - echo "Or perhaps you might print out some debugging details"

after_script:
  - echo "After script section"
  - echo "For example you might do some cleanup here"

build1:
  stage: build
  script:
    - echo "Do your build here"

test1:
  stage: test
  script:
    - echo "Do a test here"
    - echo "For example run a test suite"

test2:
  stage: test
  script:
    - echo "Do another parallel test here"
    - echo "For example run a lint test"

deploy1:
  stage: deploy
  script:
    - echo "Do your deploy here"

Build a Docker image with CI/CD and push to the GitLab registry

# To contribute improvements to CI/CD templates, please follow the Development guide at:
# https://docs.gitlab.com/ee/development/cicd/templates.html
# This specific template is located at:
# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Docker.gitlab-ci.yml

# Build a Docker image with CI/CD and push to the GitLab registry.
# Docker-in-Docker documentation: https://docs.gitlab.com/ee/ci/docker/using_docker_build.html
#
# This template uses one generic job with conditional builds
# for the default branch and all other (MR) branches.

docker-build:
  # Use the official docker image.
  image: docker:latest
  stage: build
  services:
    - docker:dind
  before_script:
    - docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY
  # Default branch leaves tag empty (= latest tag)
  # All other branches are tagged with the escaped branch name (commit ref slug)
  script:
    - |
      if [[ "$CI_COMMIT_BRANCH" == "$CI_DEFAULT_BRANCH" ]]; then
        tag=""
        echo "Running on default branch '$CI_DEFAULT_BRANCH': tag = 'latest'"
      else
        tag=":$CI_COMMIT_REF_SLUG"
        echo "Running on branch '$CI_COMMIT_BRANCH': tag = $tag"
      fi
- docker build --pull -t "$CI_REGISTRY_IMAGE${tag}" .
    - docker push "$CI_REGISTRY_IMAGE${tag}"
  # Run this job in a branch where a Dockerfile exists
  rules:
    - if: $CI_COMMIT_BRANCH
      exists:
        - Dockerfile

Rajesh Kumar

I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I am working at Cotocus. I blog tech insights at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at I reviewed , and SEO strategies at Wizbrand. 

Please find my social handles as below;

Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at PINTEREST
Rajesh Kumar at QUORA
Rajesh Kumar at WIZBRAND