Skip to content

[v10] Prepare for Dockerfile-teleterm removal#21306

Merged
ravicious merged 3 commits intobranch/v10from
ravicious/v10/prepare-for-20032-backport
Feb 7, 2023
Merged

[v10] Prepare for Dockerfile-teleterm removal#21306
ravicious merged 3 commits intobranch/v10from
ravicious/v10/prepare-for-20032-backport

Conversation

@ravicious
Copy link
Copy Markdown
Member

Backport #20032 (sort of).

This is the equivalent of #21299 for v10 where I've ran into the same issue.


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 branch. Once this commit lands in v10, 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 branch.
Once this commit lands in v10, I should be able to make CI pass for the
backport PR.
@ravicious ravicious enabled auto-merge (squash) February 7, 2023 10:59
@ravicious ravicious disabled auto-merge February 7, 2023 11:07
@ravicious ravicious enabled auto-merge (squash) February 7, 2023 11:18
@ravicious ravicious merged commit 9d5d966 into branch/v10 Feb 7, 2023
@ravicious ravicious deleted the ravicious/v10/prepare-for-20032-backport branch February 7, 2023 14:47
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