gitlab-ci.yml file for running a pipeline only on a specific branch, using specific runners and when releasing (tag) manually.

.gitlab-ci.yml

deploy_development:
  stage: deploy
  only:
    - development # Limit this job to the staging branch
  script:
    - echo "Deploy to staging server"
    - cd /var/www/stagingadmin.example.com
    - sudo git stash
    - sudo git fetch
    - sudo git pull
    - sudo npm i
    - sudo ng build --configuration staging
    - sudo systemctl reload nginx
    - sudo chown -R nginx:nginx /var/www/stagingadmin.example.com/dist
  tags:
    - staging # use the runner called staging
  environment:
    name: staging
    url: https://staging-api.example.com/
#NOTE:#
        #the above script only run if there is a release tag on the development branch. And it will run using a runner named "staging". It will run using the gitlab-ci.yml included on the development branch. So any commands above will not work.
    
    
deploy_uat:
  stage: deploy
  only:
    - uat # Limit this job to the uat branch
  script:
    - echo "Deploy to UAT server"
    - cd /var/www/uatadmin.example.com
    - sudo git stash
    - sudo git fetch
    - sudo git pull
    - sudo npm i
    - sudo ng build --configuration uat
    - sudo systemctl reload nginx
    - sudo chown -R nginx:nginx /var/www/uatadmin.example.com/dist
  tags:
     - uat-runner # use the runner called uat-runner
#     - staging
# On a single server, if deploying multiple branches on diffrent folders, then single runner is only required!
# above, we can either use uat-runner or runner named staging.
  only:
  - tags # only run when creating a new release	
  environment:
    name: uatadmin
    url: https://uatadmin.example.com/