Literate builds?

This sounds pointlessly complicated compared to just a shell script with comments that does the same thing.

It looks like these guys are picking up ideas from the travis-ci.org project, which uses a &quot;.travis.yml&quot; file for configuration-<p><a href="https://github.com/tedivm/Stash/blob/master/.travis.yml" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tedivm&#x2F;Stash&#x2F;blob&#x2F;master&#x2F;.travis.yml</a><p>This has huge advantages, especially in conjunction with things like git or github. With travis ci it&#x27;s trivial for testing to be setup on new branches or even forks. We use Jenkins at work, and I&#x27;m excited to extend that level of functionality there.

If you don&#x27;t like the sound of<p>&quot;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&#x27;s source control.&quot;<p>then you might enjoy CircleCI (<a href="https://circleci.com" rel="nofollow">https:&#x2F;&#x2F;circleci.com</a>).<p>We&#x27;ve always believed in understandable configuration checked into source control, with sane defaults and configuration over convention. The configuration (<a href="https://circleci.com/docs/configuration" rel="nofollow">https:&#x2F;&#x2F;circleci.com&#x2F;docs&#x2F;configuration</a>) 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.

This is based on Don Knuth&#x27;s Literate Programming: <a href="http://en.wikipedia.org/wiki/Literate_programming" rel="nofollow">http:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Literate_programming</a> - but applied to build scripts.<p>(Readme is docs + executable)

I think one useful feature might be the ability to export existing Jenkins build jobs to the README files. Some ppl might be more comfortable with Jenkins interface rather than writing the README files from scratch.

Congratulations! You have invented the Makefile.