Compiling C code with puppet or whatever seems a little weird to me, to be honest :) If you want to keep your data externally, there are some good options for

Compiling C code with puppet or whatever seems a little weird to me, to be honest :) If you want to keep your data externally, there are some good options for this. I'd read the plugin docs about variable plugins, that can easily source variables for things like etcd or Consul. A script for a given repo could be nothing more than "make go", and that actually is a pretty good practice, to keep that in source control. Still, you need something to build your code, and to have a good place to see the status. Ultimately, code still needs to be built, and orgs do want to avoid images they cannot easily recreate. That's the role of a build system and making sure the process to create those artifacts is in source control. I should also mention that your build script CAN be sourced from source control. In your .vespene file, just say "script: <path>. However, the variables in that file can be evaluated by Jinja2 variables, so for instance your security team could set up a snippet everybody could use or your feature flags could be defined from there. Another cool feature of Vespene is in each project build root all those variables appear as vespene.json files, so it can be a good tool to use to launch all kinds of automation from a web console where you want to record results.