Castor, a journey across the sea of task runners

JoliCode - JoliCodeBlog - 30/06
At JoliCode we were early adopters of Docker (since late 2013). When we discovered it, we strongly believed that this tool would fit perfectly in our dev environment and allow teams to work under the same clean and reproducible environment. However, like each new piece of software,

At JoliCode we were early adopters of Docker (since late 2013). When we discovered it, we strongly believed that this tool would fit perfectly in our dev environment and allow teams to work under the same clean and reproducible environment.

However, like each new piece of software, learning it requires time and motivation, and forcing it on each developer is always a bad idea as it can bring resignation and exhaustion. Also, even if we were convinced that the idea around Docker was really nice, we were not sure that its API and even the tool would stay the same over time.

What we needed to do then, was to hide the implementation of using this tool behind a functional interface that our team would use. When developing a project, we have a lot of needs as developer:

  • Launching / stopping the project environment (we can work on different projects);
  • Clearing the cache of the various components;
  • Migrating database schema;
  • Injecting fake data;
  • Launching tests;
  • Running quality tools;
  • …

Those needs don’t change. However what changes across...
[Courte citation de 8% de l'article original]