However, since I don't want developers using Macbooks to constantly cross compile this image, I have added a "manual" tag to the oci_image target and all other targets that depends on it. This way when a developer is just trying to run bazel build //... they don't have to worry about cross compilation. If they need to build the image, or run a container test, they can enter that specific bazel target label.
michaelschiff
commented
4 months ago
As a build systems developer, I would like the ability to add specific Bazel tags to the targets generated by the
k8s_deploymacro.In my current use case I have an
oci_imagetarget that is a dependency of ak8s_deploytarget. I have to support several different developer platforms and so I apply an automatic platform transition to the image (eg: https://github.com/aspect-build/bazel-examples/blob/main/oci_python_image/hello_world/BUILD.bazel#L60)However, since I don't want developers using Macbooks to constantly cross compile this image, I have added a
"manual"tag to theoci_imagetarget and all other targets that depends on it. This way when a developer is just trying to runbazel build //...they don't have to worry about cross compilation. If they need to build the image, or run a container test, they can enter that specific bazel target label.