DEV Community

Discussion on: How does deployment work at your organization?

Collapse
 
ben profile image
Ben Halpern

No shame in not using “fancy” CI tools. Whatever does the job.

Collapse
 
joelbonetr profile image
JoelBonetR 🥇

Obviously you don't have to be ashamed for not using "fancy" CI tools, but when you do, you'll see why people are using it.

I learned on last 10 years that technologies that meet a need stay, and technologies that don't, disappear or remain in legacy projects.

Git isn't something new (as you should know). CI scripts aren't new too, it only simplified the two-step task - where you were using git, svn, mercurial or wharever with a Rundeck or similar automation that needed to be fired manually - into a single step one where devs only need to push to master (if permissions) and it all rolls smooth into production and able to roll-back easily if needed.

If you are not using a version control service, then yes, you need to be ashamed.