4 ms·
Or a shell script. Always have a backup shell script.
by major505 4y ago
Or a shell script. Always have a backup shell script.
- roomey 4y agoProblem is who will maintain and test it. Without DR (disaster recovery) test days its worth nothing cause something will have been changed and not propagated
- plonk 4y agoUse the script in your regular CI/CD pipeline. Just add arguments for things that vary between GitHub runners and local machines, like secrets and paths.
- yakak 4y agoIt's certainly a risk to be relying on any proprietary SaaS or Cloud but I don't really get the reason to be doing CI/CD as if it can never be down. There are a lot of risks in having credentials on hot spare alternative systems you rarely need and the number of times I've really had to rollback a deployment quickly is something I can count on one hand. Isn't it better to focus on quality to not need to deploy on a moment's notice?
- plonk 4y agoYou can keep the credentials in a password manager. Presumably the sysadmin already uses the same corporate PM for his regular credentials, so this doesn't increase risk much. We're a small org but I'd be pretty annoyed if we planned a deployment on a day and ended up having to wait for GitHub to go back up. Deployments can be disruptive and we have to coordinate with other teams.
- mrweasel 4y agoI feel like most of my build or deployment pipelines always end up as just a bash script executed by the CI/CD tool anyway.
- major505 4y agoYeah. I the end is the only thing Jenkins do for me.