DragonOps CI/CD
DragonOps provides CI/CD for both GitHub and GitLab out of the box. While customizable, our template files will work automagically and will deploy to multiple environments for you.
Development lifecycle and CI/CD
With DragonOps, we abstract the infrastructure away so that you can iterate as fast as you want, without needing to care about the compute resources powering your app.
Once you’ve gotten your initial infrastructure up with DragonOps, updating your application means pushing a new image. Unless you need to make changes to your cpu/memory/port (or other infra-specific configs) your build and deploy pipeline is as simple as building your new Docker image, tagging it, and pushing to ECR.
This is built out in the base CI/CD workflow files DragonOps generates for you (with best-practice OIDC instead of static credentials) and which you can further customize anytime. By default, DragonOps prepares CI/CD for a dev, stage, and prod environment. The diagram below documents the general flow of the CI/CD in place.
When making updates to your workflows, it’s important to keep in mind that image tags are important, and must begin with the environment name.