Container deployment in Circle 2.0


I’m trying to figure out a workflow for deploying containers in Circle 2.0. My first attempt was three jobs: one for building the container and testing it, one to push it to docker repo and deploy to staging, and one to deploy to production. However, it seems that I cannot access my built container from subsequent jobs.

I can move the pushing of the container to the build step, but I’m wondering if this is really the best way? Ideally I don’t want my build to spend time pushing to the docker repo for PRs etc that I don’t want to push to staging.

As I type this I’m thinking I could restrict it more by just specifying the master branch.


This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.