Wercker is introducing Workflows, a streamlined way to manage custom Docker container pipelines for distributed apps and microservices.
Workflows can be used with AWS, CoreOS, Deis, Kubernetes and DC/OS.
We don't shill.
Check out TNW's Hard Fork.
Once a user defines a hook, the pipeline is executed in a Docker container. Those hooks can either be another pipeline (how meta!) or Git sources. Pipelines can be set-up using a registry in Wercker, or manually created. Once created, pipelines can be run parallel or sequentially.
The reach of Wercker Workflows is fairly endless. With a bit of work upfront, deployment is automated without a developer having to fiddle with Docker containers.
“We know developers need to break out of the two-step paradigm to go beyond build and deploys, and we’re excited to partner with companies and open source projects like CoreOS, Deis, Kubernetes and Mesosphere to make it happen,” said Micha Hernández van Leuffen, founder and CEO at Wercker. “Wercker Workflows provides our users with the powerful tools needed to develop for the modern cloud, which increasingly involves pushing containers to registries and notifying schedulers.”
Workflows is generally available, starting today.