Skip to content

Upgrade to v0.0.7 of google/containerregistry - #29

Merged
mattmoor merged 1 commit into
masterfrom
fix-28
May 11, 2017
Merged

Upgrade to v0.0.7 of google/containerregistry#29
mattmoor merged 1 commit into
masterfrom
fix-28

Conversation

@mattmoor

Copy link
Copy Markdown
Contributor

Switch to using the new relaxed naming to fix the linked issue.

Fixes: #28

@mattmoor

Copy link
Copy Markdown
Contributor Author

I'm just opening the PR for now to test things, I'd like to experiment with adding some better test coverage for this case.

@mattmoor
mattmoor force-pushed the fix-28 branch 2 times, most recently from 73314ba to a14fa6d Compare May 11, 2017 04:32
@mattmoor

Copy link
Copy Markdown
Contributor Author

@damienmg Do you have any good examples of how I might ~embed a test like I have in testing/top-level/ within the repo?

@damienmg

Copy link
Copy Markdown
Contributor

I don't really understand what you are asking for, can you give an example of what you would like to do?

@mattmoor

Copy link
Copy Markdown
Contributor Author

tl;dr bazelbuild/bazel#2751

I am going to move these files into a shell script that will run end to end tests and invoke it from Travis.

Switch to using the new relaxed naming to fix the linked issue.

Fixes: #28
@mattmoor
mattmoor merged commit 5918186 into master May 11, 2017
sudarshang pushed a commit to sudarshang/rules_docker that referenced this pull request Sep 26, 2019
…azelbuild#29)

Updates the Java example BUILD file to match the Java tutorial text (reverts bazelbuild/bazel@08e34e3).
sudarshang pushed a commit to sudarshang/rules_docker that referenced this pull request Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Top-level docker_build targets are broken again

3 participants