Jenkins is the industry standard when it comes to CI/CD systems. It is very extensible, has countless plugins, and generally can be made to do the job. However, it is showing its age, is complex to operate, has a limited API and most importantly pipelines written on Jenkins usually hang together with hastily written shell scripts that are hard to change, test and maintain.
EscapeKit takes a very different approach as it’s built around the concept of a release: a build builds releases, a deployment deploys a release, an operational task acts against a deployment, etc. Because build and deployment patterns are reusable in Escape, we can get rid of most of the complexity in maintaining a CI/CD pipeline and just focus on the orchestration.