Skip to content

[RFC] A proposed update to the Docker images ci_* tag pattern - #66

Open
leandron wants to merge 3 commits into
apache:mainfrom
leandron:docker-image-tags-format
Open

[RFC] A proposed update to the Docker images ci_* tag pattern#66
leandron wants to merge 3 commits into
apache:mainfrom
leandron:docker-image-tags-format

Conversation

@leandron

@leandronleandron commented Apr 8, 2022

Copy link
Copy Markdown
Contributor

This RFC proposes a new format to keep our Docker images used in CI, moving away from our current incremental numbering to a more meaningful format that contains a timestamp and the latest hash from the repository used to generate such images.

cc @areusch@driazati@Mousius@konturn@junrushao1994@masahi@gromero@mehrdadh@tqchen for visibility and reviews

This RFC proposes a new format to keep our Docker images used in CI,
moving away from our current incremental numbering to a more meaningful
format that contains a timestamp and the latest hash from the repository
used to generate such images.
Comment threadrfcs/0000-docker-image-tags.md Outdated

@driazatidriazati left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks for sending this in, looks good and should go along nicely with the work in apache/tvm#10646

@areuschareusch left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

thanks @leandron this looks great!

Comment threadrfcs/0000-docker-image-tags.md Outdated

@MousiusMousius left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This looks like a much better and more consistent format @leandron, could we also move to - or _ everywhere when we roll this out? (not tlcpackstaging/ci_cpu and tlcpack/ci-cpu)

Other than that, I spotted a few typos 😿

Comment threadrfcs/0000-docker-image-tags.md Outdated
Comment threadrfcs/0000-docker-image-tags.md Outdated
@areusch

Copy link
Copy Markdown
Contributor

@Mousius i support - instead of _ (when running docker/bash.sh, you can then use _ as a sort of rule of thumb to determine if you're referencing a variable-driven revision or a specific one)

@mehrdadhmehrdadh left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM!
Thanks for working on this!

@gromerogromero left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@leandron Just nitpicked what looks like a typo. Please see my comment inline.

Otherwise Rationale and alternatives makes sense to me and overall LGTM!

Comment threadrfcs/0000-docker-image-tags.md Outdated
Co-authored-by: Christopher Sidebottom <chris.sidebottom@arm.com>
@leandron

Copy link
Copy Markdown
ContributorAuthor

Just friendly note here, that as I'm not hearing opposition, I'll move into creating a a PR to update the documentation and reflect the changes proposed here where appropriate.

@Mousius

Copy link
Copy Markdown
Member

@leandron, looking at Docker Hub (https://hub.docker.com/_/hello-world) it would appear the convention for image names is to use - there as well (i.e. tlcpack/ci-cpu rather than tlcpack/ci_cpu) can we go for that one?

@leandron

Copy link
Copy Markdown
ContributorAuthor

@leandron, looking at Docker Hub (https://hub.docker.com/_/hello-world) it would appear the convention for image names is to use - there as well (i.e. tlcpack/ci-cpu rather than tlcpack/ci_cpu) can we go for that one?

Sure. I’ll push an updated version with this and @gromero’s suggestion as well.

Mousius added a commit to apache/tvm that referenced this pull request May 5, 2022
This gives us GoogleTest for #11202 and blocklint for #11200 but most importantly it makes use of the new and improved tags from @leandron in apache/tvm-rfcs#66Closes#11202Closes#11200
Mousius added a commit to apache/tvm that referenced this pull request May 6, 2022
This gives us GoogleTest for #11202 and blocklint for #11200 but most importantly it makes use of the new and improved tags from @leandron in apache/tvm-rfcs#66Closes#11202Closes#11200
leandron pushed a commit to apache/tvm that referenced this pull request May 6, 2022
This gives us GoogleTest for #11202 and blocklint for #11200 but most importantly it makes use of the new and improved tags from @leandron in apache/tvm-rfcs#66Closes#11202Closes#11200
@areusch

Copy link
Copy Markdown
Contributor

@leandron should we merge this? I think the change has landed in Jenkinsfile now

@areusch

Copy link
Copy Markdown
Contributor

cc @Mousius@gromero can you approve?

@gromero

Copy link
Copy Markdown
Contributor

cc @Mousius@gromero can you approve?

@leandron Hi. Are you still planing to change #66 (comment) ?

shtinsa pushed a commit to Deelvin/tvm that referenced this pull request May 17, 2022
)
This gives us GoogleTest for apache#11202 and blocklint for apache#11200 but most importantly it makes use of the new and improved tags from @leandron in apache/tvm-rfcs#66Closesapache#11202Closesapache#11200
SebastianBoblest pushed a commit to SebastianBoblest/tvm that referenced this pull request May 27, 2022
)
This gives us GoogleTest for apache#11202 and blocklint for apache#11200 but most importantly it makes use of the new and improved tags from @leandron in apache/tvm-rfcs#66Closesapache#11202Closesapache#11200
Co-authored-by: Christopher Sidebottom <chris.sidebottom@arm.com>
@leandron
leandronforce-pushed the docker-image-tags-format branch from badd25c to 8170fd3CompareJune 1, 2022 16:27
@gromero

Copy link
Copy Markdown
Contributor

@Mousius I don't have any further comments on it. Are you ok with the current state of this RFC? If so, could you please approve the changes so I can merge it? Thanks!

@Mousius

Copy link
Copy Markdown
Member

@leandron, looking at Docker Hub (https://hub.docker.com/_/hello-world) it would appear the convention for image names is to use - there as well (i.e. tlcpack/ci-cpu rather than tlcpack/ci_cpu) can we go for that one?

Sure. I’ll push an updated version with this and @gromero’s suggestion as well.

@gromero the above change is still pending as far as I can see?

@gromero

Copy link
Copy Markdown
Contributor

@leandron, looking at Docker Hub (https://hub.docker.com/_/hello-world) it would appear the convention for image names is to use - there as well (i.e. tlcpack/ci-cpu rather than tlcpack/ci_cpu) can we go for that one?

Sure. I’ll push an updated version with this and @gromero’s suggestion as well.

@gromero the above change is still pending as far as I can see?

@Mousius hrm right. So we'll need @leandron to make the next move here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

@leandron@areusch@Mousius@gromero@Lunderberg@mehrdadh@driazati@manupak