public marks

PUBLIC MARKS from Spone with tag ci

January 2017

Danger - Stop Saying "You Forgot To…" in Code Review

Danger runs during your CI process, and gives teams the chance to automate common code review chores. This provides another logical step in your build, through this Danger can help lint your rote tasks in daily code review. You can use Danger to codify your teams norms. Leaving humans to think about harder problems. She does this by leaving messages inside your PRs based on rules that you create with the Ruby scripting language. Over time, as rules are adhered to, the message is amended to reflect the current state of the code review.

November 2015

A Recipe for Rails Continuous Integration | mattbrictson.com

At its most basic, continuous integration (CI) is just a process that checks out the latest code commit and runs a script. What that script does is up to you. In this article I’ll share the script I use for my own Rails projects, and the reasoning behind it.

Gitlab CI Setup with Rails | Ultra High

I had a few problems getting up and running with docker-based gitlab-ci builds, so here’s a description of my setup. I’m using gitlab.com (not self-hosted) and their hosted CI at ci.gitlab.com BUT I am using private build runners on my own Ubuntu 14.04 server.

May 2015

Percy

Continuous visual integration for web apps

Spone's TAGS related to tag ci

code +   code review +   continuous integration +   front-end +   git +   github +   gitlab +   heroku +   rails +   ruby +   test +   vagrant +