Skip to content

tools: Put sha1 in container tag instead of name#22756

Merged
jtattermusch merged 1 commit intogrpc:masterfrom
ejona86:no-sha-in-name
Apr 24, 2020
Merged

tools: Put sha1 in container tag instead of name#22756
jtattermusch merged 1 commit intogrpc:masterfrom
ejona86:no-sha-in-name

Conversation

@ejona86
Copy link
Copy Markdown
Member

@ejona86 ejona86 commented Apr 23, 2020

Ideally instead of having names like ruby_jessie_x64_ruby_2_5 and
ruby_jessie_x64_ruby_2_6 they would have the name "ruby" with tags
containing jessie_x64_ruby_2_5/6. But fixing that would be much more
invasive. The sha1 in the tag is producing the worst effects, so this is
a case of the perfect being the enemy of the good.

Fixes #20546


I re-pushed the current images under the new name and verified that rebuilding an image works.

Ideally instead of having names like ruby_jessie_x64_ruby_2_5 and
ruby_jessie_x64_ruby_2_6 they would have the name "ruby" with tags
containing jessie_x64_ruby_2_5/6. But fixing that would be much more
invasive. The sha1 in the tag is producing the worst effects, so this is
a case of the perfect being the enemy of the good.

Fixes grpc#20546
@ejona86 ejona86 added the release notes: no Indicates if PR should not be in release notes label Apr 23, 2020
@ejona86 ejona86 requested a review from jtattermusch April 23, 2020 20:01
@jtattermusch
Copy link
Copy Markdown
Contributor

I started work on this, but never finished it master...jtattermusch:docker_tags_fix_20546

Thanks for stepping in. I'll quickly check for differences between the two branches.

Copy link
Copy Markdown
Contributor

@jtattermusch jtattermusch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@jtattermusch
Copy link
Copy Markdown
Contributor

Known failures: #22760

@jtattermusch jtattermusch merged commit 275be9c into grpc:master Apr 24, 2020
@ejona86 ejona86 deleted the no-sha-in-name branch April 24, 2020 16:11
@ejona86
Copy link
Copy Markdown
Member Author

ejona86 commented Apr 24, 2020

@jtattermusch, oh, I see. It looks like you were re-generating the docker images. Yeah, I can understand how that would slow things down, since it appears things fail to rebuild. I hacked push_testing_images.sh to do a docker pull + docker push under the new name. Even with that it took a long time; we have a lot of images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release notes: no Indicates if PR should not be in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Put SHA of interop base Dockerfile in tag, not name

2 participants