Every developer has to deal with legacy code—sooner or later. This means she or he should find a way to handle this code, in the best possible way. It doesn't necessarily mean migrating to a CI/CD workflow. Continually delivering or deploying code might not be right for you, your software project, or even your team. But even then, you should consider automation, at least for tests and the build process.
Did you know DeployBot can help you to improve team communication? Thanks to integrations for Slack and email you and your fellow developers can receive notifications about deployments automatically.
Pre- and post-deployment commands run on the server, before or after the deployment. However, this is more than just “stop everything, deploy, start everything” – let’s look at some typical scenarios and some clever examples which might improve your workflow.
Containers have been around for a long time, and it’s hard to imagine today’s devops world without them. But why is container technology so popular with sysadmins and developers? And why are containers a useful asset to your CI/CD strategy?
Looking behind the scenes: our DeployBot support team has told us about some common DeployBot mistakes and how to avoid them.