Personal Notes (English): Doing Gitlab CI CD In My Dirty Way

April 8, 2021 1:11 PM - 6 min read

I was going to setup Gitlab CI CD pipeline and also doing automatically database backup as for now I am using on-premise MySQL (installed inside my EC2). I call it 'dirty' because I didn't know how to do it properly, I didn't know how companies set it up. I never worked at tech giants, never worked at FAANG.

Database Backup

Having database installed on EC2 instance was my concern, I fear about losing the data so need to back it up manually everyday and I am sick of it.

So basically need to SSH to server and did manually

mysqldump -u USER -p PASS --opt --routines --skip-extended-insert --force "DB_NAME" > "<FILE NAME>"

I created a script to automate it. I am using Git repository to store the DB dump files. Use croonjob/crontab to continuously run the script.

So the concept basically is I set cron to run every 1 hour > clean working branch with git checkout . > get latest git changes if any > dump db > push to repo.

So here is my dirty script I copied from other source.


# MySQL DB dump to Git commit
# Dumps the specified mysql database to the given location and commits it and
# the previous database to the Git repository.
# It is assumed you have already setup the Git respository to only be the 
# a checkout of the database backup location
# To do that (in the repository): 
# $ git config core.sparsecheckout true
# $ echo sql-backup/ > .git/info/sparse-checkout
# $ git read-tree -m -u HEAD
# Author:	Aaron Gustafson, Easy-Designs LLC
# Copyright:	Copyright (c) 2011 Easy-Designs LLC
# Since:	Version 0.1

# init SSH agent
eval $(ssh-agent -s)

# add your private key
ssh-add ~/.ssh/id_rsa

# path to Git repository

# database settings

NOW=$(date +"%b%d-%Y-%H%M%S")

# clear all changes
git checkout .

# svn up the content
git pull --quiet

# dump the database using the mysql administrator - so we can see all dbs
mysqldump -u$DB_USER -p$DB_PASS --opt --routines --skip-extended-insert --force "${DB_NAME}" > "${FILENAME}"

# add everything we have - will throw a warning the dbname.sql already is added but its fine
git add .
# commit
git commit --quiet -m "SQL Database Dump "$NOW
# push
git push --quiet origin $REPO_BRANCH

Oh ya before run that scrip above, create a repo to store the db dump. My repo consist of some files, db dump, db backup script, index.js to run Nodejs cronjob.

|- db_backup.sql
|- index.js
|- package.json

Now we move to Gitlab. Create id_rsa with passphaseless (without passphase) to authenticate with Gitlab.

ssh-keygen -t rsa -b 4096 -C "[email protected]"

Don't forget adding it to authorized_keys. cat ~/.ssh/ >> ~/.ssh/authorized_keys. If you don't it's okay 🙃.

Add it to Gitlab SSH KEYS Add your public keys. cat ~/.ssh/ then copy it and paste to Gitlab.

Now I can run the cronjob for doing database backup automatically.

Staging Gitlab CI CD to AWS EC2

Please ignore if you don't see any test here 😂. Don't tell anyone 😂.

It was frustrating, spent 8 hours to make it works, finnaly I managed to do it.

Everything is similar like step above (db backup). Create passphaseless SSH KEY pair.

Don't forget adding it to authorized_keys. cat ~/.ssh/ >> ~/.ssh/authorized_keys. This one you need to add it 😇.

Add it to Gitlab SSH KEYS Add your public keys. cat ~/.ssh/ then copy it and paste to Gitlab.

O ya, for this case my database backup server is different with thi CICD server so I need create new SSH KEY pair.

Looks good, onto the next steps.

CICD in Gitlab, I need to create YML file in root directory of my repo.

I followed this article with my own modification.

Don't forget to add DEPLOY_SERVERS and PRIVATE_KEY to Gitlab CICD variable.

DEPLOY_SERVERS = my ip server

PRIVATE_KEY = my SSH private key which I created in step above.


# Node docker image on which this would be run
image: node:14.5.0

#This command is run before actual stages start running
    - 'which ssh-agent || ( apt-get update -y && apt-get install openssh-client -y )'
    - npm i
    - echo $DEPLOY_SERVERS

    - test
    - deploy

    stage: test
        - npm run prettier

    image: node:14.5.0
        - staging-dev
    stage: deploy
        - bash deploy/

Look no test kan 🤣?

I had no idea what to put in test stage so I put prettier there.

I only want deploy stage run when there is a push to staging-dev branch


# any future command that fails will exit the script
set -e

# add private key to .pem file
echo  -e "$PRIVATE_KEY" > stage.pem
chmod 600 stage.pem

# disable the host key checking.
chmod +x ./deploy/

ssh -i "stage.pem" ubuntu@$DEPLOY_SERVERS 'bash -s' < ./deploy/

# This the the prompt we get whenever we ssh into the box and get the message like this
# The authenticity of the host 'ip address' cannot be verified....
# Below script will disable that prompt

# note ">>". It creates a file if it does not exits.
# The file content we want is below
# Host *
#   StrictHostKeyChecking no

# any future command that fails will exit the script
set -e
mkdir -p ~/.ssh
touch ~/.ssh/config
echo -e "Host *\n\tStrictHostKeyChecking no\n\n" >> ~/.ssh/config


# any future command that fails will exit the script
set -e

cd /home/ubuntu/staging-api

# init SSH agent
eval $(ssh-agent -s)
ssh-add ~/.ssh/id_rsa

git checkout .

git pull gitlab staging-dev

echo which node
echo which npm
echo which pm2



# /home/ubuntu/.nvm/versions/node/v14.5.0/bin/npm i
npm i

echo "RESTART PM2"

# /home/ubuntu/.nvm/versions/node/v14.5.0/bin/pm2 restart all
pm2 restart all

If I remove PATH="/home/ubuntu/.nvm/versions/node/v14.5.0/bin:$PATH";, they will not recognize npm and pm2 command. So need to have it. use which npm or/and which pm2 to know where your npm and pm2 command are located.

So I think it should be working now.