![Spotify timer sleep](https://cdn3.cdnme.se/5447227/9-3/screenshot_3_64e629479606ee7f889a24a8.jpg)
![slack chime slack chime](https://techcrunch.com/wp-content/uploads/2015/04/4532347983_b817751ee2_o.jpg)
“Spinnaker offers a lot of agility in that respect.
![slack chime slack chime](https://addchime.com/assets/img/ss/salesforce/10-s4b-salesforce-integration.png)
In production, “If we need to scale customers on the Z-axis, and build multiple app versions with different backends to target different service providers” as deployment targets, with Spinnaker, Chime can. Robert has created a tool that allows them that agency, while empowering them to address complex use cases, for example, adding logic into the Slack commands to deploy dynamic environments into different Kubernetes clusters.
![slack chime slack chime](https://d2908q01vomqb2.cloudfront.net/2e01e17467891f7c933dbaa00e1459d23db3fe4f/2020/10/15/budget-action-4.jpg)
At any time, if the devs he enables would rather execute commands in Slack to deploy branches to environments of their choosing, they can. Meeting Chime devs where they’re cutting the straight-to-prod patch fix deployments down to zero,” Robert clarifies, and he’s done it by creating a flexible system with Spinnaker that models Chime’s culture of trust. When adding a small feature to a mobile app, for example, I might want to bypass CI wait time to deploy and experiment with behavior (raise your hand if you‘ve built an app and never done that…didn’t think so!)
![slack chime slack chime](https://ocs-pl.oktawave.com/v1/AUTH_2887234e-384a-4873-8bc5-405211db13a2/spidersweb/2017/02/amazon-chime.png)
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
![Spotify timer sleep](https://cdn3.cdnme.se/5447227/9-3/screenshot_3_64e629479606ee7f889a24a8.jpg)