skaffold

We have the entire development environment in Kubernetes. IDE is only used for code editing, which is then synced to the cluster. Auto-generated code and node_modules are synced back for code completion. That way, everyone has an identical dev environment and we don't depend on any particular IDE (want to use Emacs? sure). No setup steps, just running one script to create a new namespace with all applications running inside. Broke it, messed up an upgrade? Just destroy and redeploy. We hacked Arcanist[1] to run linters in the cluster. Modified a TypeScript file? "arc lint" will make sure your TypeScript pod is up-to-date and run the linter there, etc. We're using custom tooling which is faster than https://github.com/GoogleContainerTools/skaffold, but it's the same approach. Thinking about open sourcing it. [1]: Phabricator's CLI client

1. This is something I've found a bit painful, too -- this looks helpful: https://github.com/GoogleContainerTools/skaffold 2. Haven't tried this, but I'm aware of it - does this address your point here ? https://www.telepresence.io/ 3. Something like this? https://github.com/rycus86/docker-pycharm I agree that this could be very cool if further developed. I agree that we'll start to see deeper integration across the development environment though, as more dev-hours are spent on building up the toolchain.

Jenkins X runs in containers on kubernetes and all the builds are done in containers. You can use whatever pod template (collection of docker images) in your CI/CD pipeline: http://jenkins-x.io/architecture/pod-templates/ Yes we can support things like parallel steps & tests spinning up separate clusters, namespaces or environments (we do this ourselves to test Jenkins X). We delegate to an OSS tool called Skaffold to actually build docker containers that gives us the flexibility to use different approaches for docker image creation (e.g. kaniko or Google Container Builder or use the local docker daemon etc) https://github.com/GoogleContainerTools/skaffold Using Kubernetes as an engine for orchestrating containers works very well - thats kinda what Kubernetes was designed for. Though you are free to extend & integrate tools like ActiveMQ

Agreed! Jenkins X uses Skaffold to do the docker image building so can be configured to use kaniko or Google Container Builder etc https://github.com/GoogleContainerTools/skaffold

Google released a tool to help with continuous deployments called skaffold [1]. Haven't used it myself (just using bitbucket pipelines) but looks like it's a relevant tool to this. Nice. [1]: https://github.com/GoogleCloudPlatform/skaffold