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

Build: use ubuntu-20.04 image for setup VCS step #8930

Merged
merged 3 commits into from
Feb 17, 2022

Conversation

humitos
Copy link
Member

@humitos humitos commented Feb 16, 2022

We were always using readthedocs/build:latest to run all the VCS steps (e.g.
git clone). That image had an old ca-certificates Ubuntu package that does
not contains the newer Lets Encrypt certificate and because of that many git
command failed.

Now, we had rebuilt the ubuntu-20.04 image which includes a newer version of
this package and we are defining this image to be used by default in the setup
VCS step. The main goal is to avoid calling apt-get install ca-certificate on
each build and reduce this overhead.

Closes #8555

We were _always_ using `readthedocs/build:latest` to run all the VCS steps (e.g.
`git clone`). That image had an old `ca-certificates` Ubuntu package that does
not contains the newer Lets Encrypt certificate and because of that many git
command failed.

Now, we had rebuilt the `ubuntu-20.04` image which includes a newer version of
this package and we are defining this image to be used by default in the setup
VCS step. The main goal is to avoid calling `apt-get install ca-certificate` on
each build and reduce this overhead.
@humitos humitos requested a review from a team as a code owner February 16, 2022 22:40
@humitos
Copy link
Member Author

humitos commented Feb 16, 2022

I QAed this locally with nngt project and it did worked!

Copy link
Contributor

@agjohnson agjohnson left a comment

Choose a reason for hiding this comment

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

Looks good! There are a couple new F in the tests that seem related to this change though. Seems related to the parameter change, so pretty minor.

We need this because there are some attributes that are passed only to
DockerBuildEnvironment but are not allowed in LocalBuildEnvironment (e.g.
`container_image`).

As LocalBuildEnvironment is used in the tests, they were failing because it
doesn't accept this argument.

Again, we should refactor our test's code to completely remove
LocalBuildEnvironment and rely 100% on DockerBuildEnvironment.
@humitos
Copy link
Member Author

humitos commented Feb 17, 2022

I updated the code to make the tests pass.

@humitos humitos merged commit f282427 into master Feb 17, 2022
@humitos humitos deleted the humitos/use-ubuntu-image-setup-vcs branch February 17, 2022 19:14
Sign up for free to 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.

Invalid certificates (Let's Encrypt related)
3 participants