Michael DeHaan

If you tried the setup process earlier and hit a few repo location problems or had problems with init scripts, those should be fixed now. Stop by the forum if you have any install questions or problems and we'll get them sorted out quickly!

Build status: Blue. No, yel-- auuuuuuuugh! ..... http://docs.vespene.io/launch_questions.html …

If you want to make use of variables from Consul or etcd or pretty much anything within your build scripts, write a variable plugin (contributions welcome!) http://docs.vespene.io/plugins.html  and you can easily suck them in from afar

Vespene pipelines can use output variables - http://docs.vespene.io/variables.html  to pass image IDs, bucket names, and more between stages of a CI/CD pipeline

Vespene snippets are inspired by earlier work on Cobbler and allow reuse of common build stanzas among diverse build scripts - http://docs.vespene.io/variables.html 

Vespene builds can be securely isolated using either sudo or docker containers using any base image - http://docs.vespene.io/workers.html  - builds happen inside a docker build process and then the build roots are copied out, no persistent containers are required.

Notice how pretty much all "DevOps" tools consume JSON or YAML? Vespene variables are made available in the build root as "vespene.json", easily consumable by anything that can use JSON or YAML as input - http://docs.vespene.io/variables.html 

Vespene is less than 5000 lines of code, thanks to the power of Python and Django! Have cool ideas? Check out http://docs.vespene.io/development_guide.html … and stop by the forum!

Schedule repeatable builds and automation actions - http://docs.vespene.io/scheduling.html  - or kick them off on commit with webhooks - http://docs.vespene.io/webhooks.html 

Automated install scripts are provided for CentOS 7 (and compatible distros) and Ubuntu Bionic Beaver to start, but it's also easy to hack on Vespene on a Mac. Other OS'es to come and quite welcome - http://docs.vespene.io/setup.html 

Control build sprawl in large microservices infrastructures. Jinja2 templating is available in build scripts using variables from both internal and external sources - http://docs.vespene.io/variables.html 

Nearly everything is a plugin and modular - including most of the business logic. Over time there may even be more types - http://docs.vespene.io/plugins.html 

Continuous deployment pipelines? We've got that - http://docs.vespene.io/pipelines.html 

Vespene projects can be defined in github with .vespene files - (and you can even get started with an import without them!) - http://docs.vespene.io/importing.html 

Want to make an easy interactive console around launching a deployment script? Need to give the support team an easy way to perform some complex actions? We've got you covered - http://docs.vespene.io/launch_questions.html …

Vespene features integrated SSH-agent code. Not only for git+SSH checkouts, but it can automatically provide keys to your build scripts too, all without sharing them directly with the full team. - http://docs.vespene.io/access.html