Hydra tutorial series — Part 7: CI and deployment
· 14 min read
In part 5 you ran Hydra by hand: build the images, run a stage with dev-run.sh, label an issue. That is the right way to learn Hydra, but it is not how it runs day to day. In production nobody starts containers from a terminal. Instead a scheduled flow notices the labelled issue and has each stage run for it, with no one at the keyboard. This part explains that path, where the pre-built images fit in, and the three deployment models behind it.