Hi, I've been using GoCD running in Docker containers for some time, it works fine and as expected. Upgrading typically means * making a backup (in case things go bad), * rebuilding our images (update the FROM line of server and agent images (we add SSH keys etc)), and * start up again, MAKING SURE the server container re-uses the same volumes for the config (git) repo, artifacts and H2 database.
This works fine, as long as those volumes survive and are kept around for later use. We'd now like to move away from having dedicated/permanent volumes, as well as automate this entire process. Has anyone done this, who'd also be willing to share their solution/issues? We Must: M1) preserve configuration M2) preserve pipeline and stage counters For M1, we can pull/clone the repo ever x minutes, after startup, use API to upload latest XML (we don't need to preserve config history). For M2, we could pull history from API, and try to keep track of stage counters. We Could: * preserve artifacts & logs * preserve run history / Fredrik -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
