CI/CD is useful regardless of which language you’re using. Sooner or later some customer is going to yell at you because you didn’t discover the fatal error before deploying.

[–] jabberati@social.anoxinon.de -2 points 2 years ago (2 children)

@magic_lobster_party @alphacyberranger @unsaid0415 CI/CD won't prevent that. I wonder what it is for. Not using the CPU on my laptop for tests? And why would I want to commit before knowing the tests pass?

[–] Stumblinbear@pawb.social 1 points 2 years ago

He says as though he's never had two PR merges conflict logically with each other

[–] AstridWipenaugh@lemmy.world 1 points 2 years ago

CICD isn't an alternative to testing your own work locally. You should always validate your work before committing. But then once you do, the CICD pipeline runs to run the tests on the automation server and kicks off deployments to your dev environment. This shows everyone else that the change is good without everyone having to pull down your changes and validate it themselves. The CICD pipeline also provides operational readiness since a properly set up pipeline can be pointed to a new environment to recreate everything without manual setup. This is essential for timely disaster recovery.

If you're just working on little projects by yourself, it's usually not worth the time. But if you're working in anything approaching enterprise grade software, CICD is a must.