-
Notifications
You must be signed in to change notification settings - Fork 694
added support for user defined tags on generated container_import
r…
#1274
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's not really any way that I can think of to test this, other than manually verifying the produced BUILD file does have the right tags, and checking the expected behavior. So can you just verify this is working as intended for you and then we can merge, change is simple enough
@nlopezgi I tested this locally with the |
Can you please run buildifier on container/pull.bzl and update your branch? Should be good to go once the buildkite presubmit passes; I can then run gcbtests and approve and merge if everything passes. |
Thanks @nlopezgi. Done! The build seems to fail on an unrelated issue. I think the cause is:
|
Yeah there's, an infra issue with our CI atm, I'll re run once that is resolved. |
/gcbrun |
Updating branch to see if Buildkite issue is now resolved |
/gcbrun |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nlopezgi, sha1n The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@nlopezgi this is my proposed fix for #764
I tested this with
--experimental_allow_tags_propagation
and it works as expected. Without the flag, theGUNZIP
andGZIP
actions will run against remote-cache. But this is expected and this PR solves a more generic case and is not specific to remote-caching.A few notes:
container_pull
repo rule.. will be happy to hear other suggestions.