-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Use latest docker images as default #5155
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
7cc7dda
Default on Docker image: readthedocs/build:3.0
humitos df9ef54
Include new Docker images in settings
humitos 293c4b8
Use DOCKER_* settings for config validation
humitos 9bb3ced
Accept numbered versions for V1 and named ones for V2
humitos ed9eee8
Allow all numbered versions plus stable and latest as valid images
humitos 2bf0f88
Do not accept `testing` or `5.0rc1` as valid image
humitos ee64002
Default Docker image to `latest` in YAML v1 and v2
humitos b829d70
Make test pass the decisions made
humitos 4cd9133
Lint issue fixed
humitos caaff03
Make valid_build_images a @property
humitos a7770c0
Lint
humitos File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The default build image are different from v1 and v2. v1 uses 2.0, v2 uses
latest
.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.
🤔 I think both should use
stable
as default image.Having different image default for v1 and v2 is confusing. Also, defaulting to a fixed version like
2.0
will make us to be tied to that version. Besides,2.0
is deprecated.On the other hand, I think that defaulting to
latest
is not a good practice since it may be not tested enough to use it widely as default.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.
We will be changing the builds for users using v1, we shouldn't change the spec.
Using latest was decided in #4084 (comment)
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.
We can default to
latest
as that comment says. I don't agree, but it's not a huge problem, though.Regarding default to
2.0
forv1
is not a good decision to me. I'd like to change that tostable
(this is a non-breaking change and actually is more stable). Right now, we are defaulting to ConfigV1 for new projects, and ConfigV1 is defaulting to2.0
, so in the end, all new projects will be using a2.0
which is a deprecated build image.I'm -1 on defaulting to a deprecated Docker build image for new projects.
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.
If there isn't a technical limitation to why we can't use the same image for both, I agree that both should point to the same image.
However, I don't think that image should be
stable
by default. Everyone should be usinglatest
now, or3.0
by default. Not continue to use2.0
. Thestable
image was meant as a way for users to opt into an older image if they are having serious problems with the newer image.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.
To clarify, terminology here has swapped, as per our conversation on docker image versioning.
latest
doesn't mean bleeding edge to us, that is what RCs are.latest
is the most recent image that we have vetted and consider production ready.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.
OK.
stable
is3.0
at this moment. Anyways, usinglatest
should not be a problem and will keep our projects up to date, but we will need to careful when releasing new images, since the change will affect the projects immediately.Considering that we have a feature flag now to use
testing
, this will allow us to test RCs easily.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.
I think there isn't a technical limitation, but I'm not 100% sure yet.
I will default both to
latest
an test locally how it behaves as a first step.