Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a wpt docker-push command #23742

Merged
merged 2 commits into from Jun 1, 2020
Merged

Add a wpt docker-push command #23742

merged 2 commits into from Jun 1, 2020

Conversation

jgraham
Copy link
Contributor

@jgraham jgraham commented May 22, 2020

No description provided.

@wpt-pr-bot wpt-pr-bot temporarily deployed to wpt-preview-23742 May 22, 2020 11:47 Inactive
Copy link
Member

@Hexcles Hexcles left a comment

Choose a reason for hiding this comment

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

Sorry for the delay; just back from a vacation.

tools/docker/frontend.py Outdated Show resolved Hide resolved
tools/docker/commands.json Outdated Show resolved Hide resolved
def parser_push():
parser = argparse.ArgumentParser()
parser.add_argument("--tag", action="store",
help="Tag to use (default is taken from .taskcluster.yml)")
Copy link
Member

Choose a reason for hiding this comment

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

I'm a little hesitant about this. Tags can be overwritten on Docker Hub, so if someone (with the right permissions) runs wpt docker-push without bumping the version in the tag first, we'd end up changing the currently used Docker image on Taskcluster without having to land any change in code.

I'd much prefer defaulting to current version + 0.01, and either update the yaml files automatically or prompt the user to to do that (if editing is hard with pyyaml).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh wow, I just assumed… and apparently you need to buy enterprise to fix this. Anyway I added a check on whether the tag already exists or not. I rather like the workflow where it reads the tag from the yaml files, and as you note rewriting the files with the updated data is tricky to do in a nice way.

@wpt-pr-bot wpt-pr-bot temporarily deployed to wpt-preview-23742 May 28, 2020 10:38 Inactive
Copy link
Member

@Hexcles Hexcles left a comment

Choose a reason for hiding this comment

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

LGTM % nits

tools/docker/frontend.py Outdated Show resolved Hide resolved
tools/docker/frontend.py Outdated Show resolved Hide resolved
Co-authored-by: Robert Ma <robertma@chromium.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants