The good people of CircleCI provide a basic service for free and that is very nice.

Yesterday I initially embarked in setting up a Jenkins server on Internet using one of my VPS instances, and I went as far as running a Docker container Jenkins with self-installation of plugins. A very simple Dockerfile:

FROM jenkins
COPY plugins.txt /usr/share/jenkins/plugins.txt
RUN /usr/local/bin/install-plugins.sh bitbucket

Docker run command:

docker run -d -u root -p 127.0.0.1:8080:8080 -p 127.0.0.1:50000:50000 -v /root/jenkins:/var/jenkins_home -n jenkins jenkins 

It was then that I discovered that months before I had already created a webhook to CircleCI in my Jekyll Bitbucket repo.

So I abandoned the Jenkins container (although it’s nice to see how quickly one can be up and running), and went back to complete the abandoned CircleCI setup.

I had to add a circle.yml file and define some testing with the help of this very helpful post.

To get started I am using a very basic configuration like the one shown in the post

  machine:
    environment:
      NOKOGIRI_USE_SYSTEM_LIBRARIES: true # speeds up installation of html-proofer

  dependencies:
    post:
      - bundle exec jekyll build

  test:
    post:
      # - bundle exec htmlproofer ./_site --allow-hash-href --check-favicon --check-html --disable-external
      - bundle exec htmlproofer ./_site --allow-hash-href --check-html --disable-external

  deployment:
    prod:
      branch: master
      commands:
        - rsync ......

I don’t have favicons, maybe I should?

Next step is adding comments using a serverless service, I am thinking webtask.io.