Jenkins is good enough, any tool that you or your team already "knows" is good enough. First, try to move any scripts that you might have and any dependency on

Jenkins is good enough, any tool that you or your team already "knows" is good enough. First, try to move any scripts that you might have and any dependency on yours or your team members workstation to a dedicated CI/CD tool (like Jenkins). Second, from the beginning, make sure to follow the "best practices" on how to handle credentials and secrets. Don't add in plain text any credentials or SSH keys. Third. from that point on, you can start looking at more complex tooling and/or deployment strategies (canary deployments, blue-green deployments, etc) to make sure updates on your applications won't break production. CI/CD pipelines don't have to be fancy in order to work properly.