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

[v11] Prepare for Dockerfile-teleterm removal #21299

Merged
merged 2 commits into from
Feb 7, 2023

Conversation

ravicious
Copy link
Member

@ravicious ravicious commented Feb 6, 2023

Backport #20032 (sort of).

make protos-up-to-date and thus make grpc is now run as a part of CI. Thus I cannot just change the buildbox Dockerfile when backporting #20032 as it will use the old buildbox image to lint protos. That old image won't be able to compile JS protos.

I extracted relevant Dockerfile changes from the backport PR (#21064). Once this commit lands in v11, I should be able to make CI pass for the backport PR.

`make protos-up-to-date` and thus `make grpc` is now run as a part of CI.
Thus I cannot just change the buildbox Dockerfile when backporting #20032
as it will use the old buildbox image which won't be able to compile JS
protos.

I extracted relevant Dockerfile changes from the backport PR (#21064).
Once this commit lands in v11, I should be able to make CI pass for the
backport PR.
@ravicious ravicious enabled auto-merge (squash) February 7, 2023 10:58
@ravicious ravicious disabled auto-merge February 7, 2023 11:07
@ravicious ravicious enabled auto-merge (squash) February 7, 2023 11:08
@ravicious ravicious merged commit 767c18e into branch/v11 Feb 7, 2023
@ravicious ravicious deleted the ravicious/v11/prepare-for-20032-backport branch February 7, 2023 11:22
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.

3 participants