Robert explains that, in some instances, it makes sense for developers to deploy straight to a test environment, bypassing CI.

Luckily, according to Robert, its high-trust, growth minded culture and workflows have supported the evolution.Ĭhime’s culture also provides flexibility that highlights Spinnaker’s power to accelerate digital transformation. So, containerization formed an important milestone in Chime’s continuous delivery adoption. It’s based on configuration management tools such as Salt, and thus not containerized, but pointed at long-lived infrastructure.

However, it hasn’t always been this way Chime has roots in a legacy build environment, largely for Ruby-on-Rails development. Via pipelines, merged release branches are auto-deployed from a continuous integration (CI) solution, through QA to production with no human interaction interaction. Chime’s continuous delivery is based on Spinnaker, driven with signal-based GitOps. Last month I had the pleasure of chatting with Robert Keng, a Lead SRE at Chime, about a Slack-integrated ChatBot he recently built to facilitate lightweight, direct deployments for developers. Originally posted on the Spinnaker Community blog, by Rosalind BenoitĬoming soon from Chime to OSS, a software delivery chatbot which uses Slack to deploy apps via Spinnaker

Slack chime