PUBLIC MARKS with tag ci

Build better mobile applications, faster Save time, money, and developer frustration with fast, flexible, and scalable mobile CI/CD that just works.

Scalingo est un PaaS souverain Français qui permet d'héberger magiquement votre application sans avoir à gérer de serveurs. L'hébergement cloud devient facile et instantané. Scalingo autonomise les équipes de développeurs pour qu'elles gèrent elles-mêmes le déploiement continu de leurs projets web.

Deploy complex application, seamlessly Just push your code, we handle the rest

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.

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.

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.