I'm looking into CI/CD options for a project, but I'm in a tough spot where automated CI/CD is off-limits, even on a local machine that's not online. It's unlikely I'd get approval for simple automation like Powershell scripts either. What can I do to implement some CI/CD practices under these restrictions without explicitly calling it CI/CD or automation?
2 Answers
It's baffling to me that a tech company wouldn't allow any form of automation. I'd recommend digging into the reasons behind this decision. Maybe you could show how certain practices, like GitOps, can enhance security while still being compliant. It could help bring the decision-makers around.
Exactly, GitOps can keep track of everything while ensuring that multiple people sign off on changes.
Honestly, if your workplace is that restrictive, it might be worth considering a job change. There are companies out there that embrace automation in software development, and this kind of limitation is a big red flag.
That's on my mind for the new year. It feels like a dead end here.
For sure. Using controlled processes like git approvals might help calm their fears about automation.