Nomad dev here. Great post! Hopefully I can provide some insights:<p>> 1. Templated job files.<p>While parameterized jobs[0] are a step toward templated jobs, they unfortunately don't address your use case. We'll be adding `-var` options to `run` in 0.7 to allow templating normal jobs like you can template jobs.<p>In the meantime I think what you're doing is pretty good and should integrate well into a CI/CD pipeline for automating deploys of new builds.<p>You could consider a specialized templating tool instead of sed like m4, a jinja-based tool like j2cli, or even consul-template.<p>A number of users also bypass `nomad run ...` and run jobs through our HTTP API instead.[1] While this takes more code, it's easiest to build into existing deployment tooling (CI/CD, chatops, chef, etc) and obviously allows easy manipulation.<p>> 2. Better documentation.<p>Absolutely. We're acutely aware of the need for more comprehensive docs. Expect a "Guides" section to appear in the near future to cover common use patterns like yours!<p>> 3. Explicit support for artifact versioning?<p>Probably not going to happen as it would be little more than an opaque meta var to Nomad.[2]<p>Although in the upcoming 0.5.5 release we do support Git and hg URLs for artifacts, so you could pull down code from a tag.[3]<p>We do have other artifact features planned for the near future though (like caching so common artifacts shared between jobs aren't downloaded multiple times), so perhaps some sort of versioning will be added. Not sure what the exact semantics will be yet.<p>[0] <a href="https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch/" rel="nofollow">https://www.hashicorp.com/blog/replacing-queues-with-nomad-d...</a><p>[1] <a href="https://www.nomadproject.io/docs/http/job.html#put-post" rel="nofollow">https://www.nomadproject.io/docs/http/job.html#put-post</a><p>[2] <a href="https://www.nomadproject.io/docs/job-specification/artifact.html" rel="nofollow">https://www.nomadproject.io/docs/job-specification/artifact....</a><p>[3] <a href="https://github.com/hashicorp/go-getter#git-git" rel="nofollow">https://github.com/hashicorp/go-getter#git-git</a>