Lucas Wilson-Richter, one of our Senior Engineers, spoke at the July Devops Melbourne meetup about our experience moving from Continuous Delivery (where the main line can potentially be deployed at any point) to Continuous Deployment (where the main line gets deployed automatically on every update). The video is now available on YouTube, or you can watch it here: Video by Andrew Jones, used with our thanks.
Image: “Delivery Dog” by AnimalCrew We’ve been doing Continuous Delivery for a while at Redbubble, and we’ve learned quite a bit, so I thought I’d share a few questions you should ask when making the transition from Continuous Integration to Continuous Delivery. Hopefully our experience can help you, whatever stage you’re at. But first, a quick refresher on what exactly Continuous Delivery is. When we are doing Continuous Delivery, we are doing Continuous Integration by definition. In addition to having an automated build, Continuous Delivery requires that any passing build can be deployed at any time, at the push of a button. This is more advanced than Continuous Integration, in which we always know whether our software builds
Image: “Surfing kangaroo and friends” by pixbyrichard The Australian-English dialect is unique in many aspects, with a large number of colloquial terms that are often impenetrable to non-Australian English speakers. This phenomenon extends to technical terminology as well. This document is an attempt to assist non-Australian English-speaking technical professionals when communicating with their Australian counterparts. For a guide on pronunciation of Australian English, see https://en.wikipedia.org/wiki/Australian_English_phonology bludger, n. a sleep command (suggests a sub-optimal practice) e.g.: “Bugger cron for a joke – sling a bludger in there” meaning: “I do not believe that scheduling a command will be worth the effort. Let us instead call sleep.” bordit, v. draw something on the whiteboard e.g.: “Bordit, mate!” meaning: “My friend, I am struggling to comprehend your
There are some tasks in a programmer’s life that come up again and again. Creating classes in an often-repeated pattern. Adding entries to some boring but important list defined in code. Those tasks that make you think “This is so tedious! I do this over and over! There has to be a better way!” Fortunately, there is.