Configuring a GitLab CI pipeline for Rails, MongoDB, and Rspec

tony — Mon, 29 Apr 2019 11:28:12 +0000

Gitlab has a free private git repository service and an integrated CI service that can be configured to suit our needs. To know more about setting up Gitlab CI, check out our [blog post](link here)

Including MongoDB in CI build system

Instead of installing and starting MongoDB manually, we can use the Gitlab mongo service. A Gitlab service is just another Docker image that runs during your job and is linked to the main image. The first step is to include the latest MongoDB image to the build system. Add this to your .gitlab-ci.yml

services:
- mongo:latest

Add the MONGODB_URI variable

Add a variables section within .gitlab-ci.yml to set the MONGODB_URI variable.

variables:
MONGODB_URI: mongodb://mongo:27017/test_db

Add config/mongoid.yml ile

Add a file config/mongoid.yml.gitlab with the following contents

test:
  clients:
    default:
      uri: <%= ENV['MONGODB_URI'] %>

Override config/mongoid.yml with config/mongoid.yml.gitlab

We need to override the local test configuration with the above settings specific to CI. Add the following to the before_script section of .gitlab-ci.yml

before_script:
  - cp config/database.yml.gitlab config/database.yml

That’s it fellas, you are all set

Summary

The complete .gitlab-ci.yml

image: starefossen/ruby-node:latest
services:
  - mongo:latest
variables:
  MONGODB_URI: mongodb://mongo:27017/test_db
before_script:
  - RAILS_ENV=test bundle install --jobs $(nproc) "${FLAGS[@]}"
  - cp config/mongoid.yml.gitlab config/mongoid.yml
  - RAILS_ENV=test bundle exec rake db:create db:migrate
test:
  script:
    - bundle exec rspec

the contents of config/mongoid.yml

development:
  clients:
    default:
      database: dev_db
      hosts:
        - localhost:27017
      options:
        read:
          mode: :primary
        max_pool_size: 10
production:
  clients:
    default:
      uri: <%= ENV['MONGODB_URI'] %>
      pool_size: <%= ENV['DB_POOL_SIZE'] %>
test:
  clients:
    default:
      database: test_db
      hosts:
        - localhost:27017
      options:
        read:
          mode: :primary
        max_pool_size: 1

and config/mongoid.yml.gitlab

test:
  clients:
    default:
      uri: <%= ENV['MONGODB_URI'] %>

May you have a green build! :-)]]>

How to format Git log for meaningful information

harikrishnan — Mon, 30 Jan 2017 12:42:55 +0000

Git is a wonderful piece of software that makes life easier and more productive for a programmer. But sadly most developers don’t use it up to their full potential so we are going to blog about various simple and advanced usages of git as a series. In the first article of the series, we are going to talk about git logs. Git log is a great feature, that allows us to keep track of our works. There are different options available under git log command, which help us to customize the output of git log and also to filter the log.

Git Graphs

git log --graph --decorate --oneline

The –graph option draws a graph representing the branches and its structure of commit history. –oneline is used to display commit message and its hash in a single line, which is used along with –decorate, which helps us to easily see which commit belongs to which branch.

Custom formatting

git log --pretty=format:""

This lets you display each commit however you want in printf style. For example %cn, %h and %cd which represents committer name, abbreviated hash and committer date respectively.

git log --pretty=format:"%cn committed %h on %cd"

Filtering the output

Git log can be filtered by different filters and format output

By amount

git log -

It displays latest n commits and its output. For example

git log -3

Will display latest 3 commit details

By date

git log --after=
git log --before=

Using --after and --before, we can get logs after or before the specified date. You can also use these both to get logs between two dates Example

git log --after='24-10-2016'
or
git log --since='24-10-2016'

--since and and --until are synonym for --after and --before

git log --date=

--date flag is used to format the output of the date. There are different option available for --date flag such as short, iso8601, relative, etc…

By Author

git log --author=

When you are only looking for commits by certain user you can --author flag. You can also use regular expressions for this.

git log --author='John\| Mary'

By message

git log --grep=''

When you want to search for log with certain string using --grep flag. You can use -i option if you want ignore the case.

By file

git log -- something.rb incredible.rb

When you want to get log only on some files you can specify files after -- flag

By Content

Git log allows you to get logs of files containing certain string. You can specify string using the -S flag

git log -S"Hello World!"

Format options available

git log --pretty=format:''

Git log format options

%H  - Commit hash
%h  - Abbreviated commit hash
%T  - Tree hashes
%t  - Abbreviated tree hash
%P  - Parent hashes
%p  - Abbreviated parent hashes
%an - Author name
%ae - Author email
%ad - Author date (format respects the --date=option)
%ar - Author date, relative
%cn - Committer name
%ce - Committer email
%cd - Committer date
%cr - Committer date, relative
%s  - Subject
%B  - Message

Example

git log --pretty=format:"%B on %ad with hash %h by %an" --date=short

That was a bit on how we can use Git log, and specifically on how to format the output. Leave your comments, questions, and doubts in the comment section in case you need to reach me.]]>

git – redpanthers.co