Build and Push Docker image in CI

[tomgun132]

Hi, I've been reading about docker and CI using Pants. Locally, it works great and really simplifies the dockerfile.
However, right now I want to put the build and push docker image process in the CI. Currently, my team uses the template from build-push-actions from docker. My questions are:

• Is it possible to replace the build and push action step from here and change it with pants publish ::?
• From this page, it says that pants publish builds image and push it to the registries. This mean, I can skip pants package, am I correct?
• I have 2 variables that needs to be obtained from 2 github's action steps to build and push the images: one as docker's build_args, one as the image's tag. I assume that the latter can be put into build_args as well. However, can I do something like this: IMAGE_TAG=${{steps.gen_tag.outputs.tag}} SOME_SECRET=${{steps.auth.outputs.token}} pants publish ::
• do the args from this answer can be applied to pants publish?

I'm sorry for many questions but I've been stuck on this part of developing with Pants. Thank you.

[kaos]

Hi!

• Is it possible to replace the build and push action step from here and change it with pants publish ::?

Yes, but you still need to handle the docker login outside of pants, and propagate any required env vars that docker or the docker auth plugin requires to work, as by default Pants strips away all your env vars before invoking sub processes. There are more details of this in our Slack channel if your search for docker auth there.

• From this page, it says that pants publish builds image and push it to the registries. This mean, I can skip pants package, am I correct?

Yes. Any packages being published will first be packaged.

• I have 2 variables that needs to be obtained from 2 github's action steps to build and push the images: one as docker's build_args, one as the image's tag. I assume that the latter can be put into build_args as well. However, can I do something like this: IMAGE_TAG=${{steps.gen_tag.outputs.tag}} SOME_SECRET=${{steps.auth.outputs.token}} pants publish ::

Yes, that's one way to get the env var into the Pants world. Then there are a few different ways to pick it up for your docker_image target.
Using env() directly in the BUILD file: https://www.pantsbuild.org/docs/targets#environment-variables
Or via the [docker] config section and build args: https://www.pantsbuild.org/docs/tagging-docker-images#using-env-vars-to-include-dynamic-data-in-tags

• do the args from this answer can be applied to pants publish?

Yes, see https://www.pantsbuild.org/docs/advanced-target-selection and for reference: https://www.pantsbuild.org/docs/reference-filter