After writing this, it separately popped up as a topic on the ‘bird’ platform, and I’m keen to start a groundswell to allow us to move the ceremonies about somewhat now.
Weekends, factories don’t work? Curious about the deeper plan here to be fair. Because surely factory software deployment is manual because things are air-gapped? How exactly do you deploy, to many sites or just one site?
Continuous Delivery is influenced by Toyota so it is good to ask about factories, but if you need to make fix on a Saturday why wait till Monday to deploy it?
Most of the time no.
Additionally, it wasn’t just Fridays, but also:
- the day before a state holiday or
- personal holidays of key developers/infra specialists that could fix a potential mess on the server.
- or if there’s no reason to, as it’s not helping the company business anyway.
- also no pushing the release if you’re not there when it finalizes(some devs doing that lost the permission to do any releases for a looong time).
- at the time when there’s a dependency after the release from someone and that can’t be accomplished;
But sometimes yes: - small changes;
- urgent fixes;
- work from home(some people were releasing during the weekend).
It depends on the site, most in my current client are 24/5, a couple are 24/7. Weekend deployment is the least disruptive.
Deployment for us is manual, yes, though the full deployment process depends on whether we’re deploying handheld movelets, database updates, SAP transports, etc
We submit to App Store and play store on Fridays for review on Fridays just to save time on the review lead time which usually take 24-48 hours so it is ready on Monday to go live once approved . So when we are off for the weekend things are still progressing and also we don’t want to risk Friday releases due to no roll back options due to app and also less staffing.
Right now, we release on every day of the week, except Friday. I’m guessing that might change as there is a big push to have more automation in place
If you are scared to release on Fridays, something is wrong. You can ignore the dysfunction (and not do Friday releases) or you can address it.
This is like not wanting to refactor code because you are scared you’ll break something. (Because you have no tests.)
Well, there isssss… the way, that releasing is equivalent to ramping up your QA resource from 2 testers to instantly having 2 million testers. If you have 2 million unique testers and environments, you can release at 5pm on a Friday with confidence can’t you?