3 ms·
That's how we roll at Cloudkick. We ship the code. We're going to get all of Rackspace to do this too if we can.
by btipling 16y ago
That's how we roll at Cloudkick. We ship the code. We're going to get all of Rackspace to do this too if we can.
- joshhart 16y agoWill you really be able to pull that off? I imagine certain parts of the code base you could use CI, but Rackspace servers cannot have downtime. If I were a Rackspace customer, I wouldn't want innovation - I'd want my boxes to never go down. And I believe that means a rigorous QA process.
- AngryParsley 16y agoIt's not always true that development is a trade-off between fast feature development and stability. If you're building a monitoring system (like Cloudkick), more features means more stability for whatever you're monitoring.
- MartinCron 16y agoIt seems like you're creating a false dichotomy between rigorous QA and continuous deployment. If you have a working and stable production system and multiple layers of test automation, rigorous QA gets easier, in that they only have to validate one change at a time.