CI/CD

Wodby provides the built-in Wodby CI to build, release and deploy your images stacks. Alternatively, you can use your own CI/CD system to build and push images to Wodby registry, for more see CI integrations. Both approaches utilize Wodby CLI to continuously build and deploy your applications in four steps:

1. Init

Wodby CLI fetches information about your application stack during wodby ci init step: Dockerfiles for services, their image, associated docker registry.

2. Build

Step wodby ci build [service] runs docker build for all (or specific) buildable services. You can optionally specify a custom Dockerfile or change the build context.

3. Release

Step wodby ci release pushes built docker images to the associated registry. By default, we provide Wodby Registry, but you can also use your own registry such as Docker Hub, for more see Docker registry integrations.

4. Deploy

Step wodby ci deploy Sends information about the build (services and their built images) to Wodby API. Wodby will then run a deployment of the built services with provided options (e.g. force deploy all services, skip post-deployment scripts).