https://github.com/tedivm/Stash/blob/master/.travis.yml
This has huge advantages, especially in conjunction with things like git or github. With travis ci it's trivial for testing to be setup on new branches or even forks. We use Jenkins at work, and I'm excited to extend that level of functionality there.
Dream result would be what happened with RVM and RBenv merging their simple "select ruby version" files in that Travis, CircleCi, Jenkins etc. all agreed on a generic .build.yml file syntax and we could just use that.
For example, at Circle, we're still experimenting with yml syntax for user-specified parallelization commands. Each different syntax we've looked at has different implications for what kinds of problems are simple, and what kinds of problems are expressible, using the syntax.
So yes, standards, but not yet :-)
"The literate plugin adds an Action to all Free-style projects that allows exporting these XML configuration snippets in a .zip file for unpacking into your project's source control."
then you might enjoy CircleCI (https://circleci.com).
We've always believed in understandable configuration checked into source control, with sane defaults and configuration over convention. The configuration (https://circleci.com/docs/configuration) is sane and human readable in yaml, yet incredibly powerful, and allows you set up a simple config in 5 minutes, and a complex config in an hour.
Back to Jenkins we went...
When you build something to work for everybody, you make something that's not really great for anybody. That's Jenkins.
Instead, we built Circle to be amazing for a small set of people (web devs deploying to Linux). If you don't fit into that group, use Jenkins.
As time goes by, we're expanding our delightfulness to other groups of people (we only supported Rails at the start, for example).
In that vein, we're rolling out the feature to give you more than 2GB of RAM at the moment, so soon you'll be in the group that can have the delightful experience too :)
I would say that the terseness of the syntax and use of pipes makes it very literate once you know enough of the low level syntax of tools like sed, grep and awk to read them likes sentence fragments joined by pipes. It's parses very linearly as each line usually reads like a complete compound "do this, then this, then this" sentence describing a bunch of steps sequentially.
Totally correct, actually. Makefiles are the cruft of ages distilled through a minimum of ten little-understood tools of the ancients, classically employing a minimum of four distinct languages. Some replacements have been popping up of late... scons seems nice.
(Readme is docs + executable)
