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

Create automated check for components on Chromium upgrade #11811

Open
bsclifton opened this issue Sep 22, 2020 · 0 comments
Open

Create automated check for components on Chromium upgrade #11811

bsclifton opened this issue Sep 22, 2020 · 0 comments
Labels
Chromium/upgrade major Major version bump. (ex: Chromium 88 to 89) Chromium/upgrade minor Minor version bump. (ex: Chromium 88.0.0.1 to 88.0.0.2) dev-concern infrastructure OS/Desktop

Comments

@bsclifton
Copy link
Member

Description

When minor or major Chromium upgrades are done, sometimes new components are added. We don't have an automated or manual process to discover what components are new (or removed)

Steps to Reproduce

  1. Do a manual upgrade of Chromium or run the minor bump job we use in Jenkins (Brave employees only)
  2. Once build is compiling, you can visit chrome://components

Actual result:

Not sure if there are new ones? We aren't storing the component IDs

Expected result:

We should be alerted there are new components or when component is removed

Miscellaneous Information:

Also see Remove unused components from brave://components and Review non-registered components

@bsclifton bsclifton added infrastructure Chromium/upgrade minor Minor version bump. (ex: Chromium 88.0.0.1 to 88.0.0.2) Chromium/upgrade major Major version bump. (ex: Chromium 88 to 89) OS/Desktop labels Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chromium/upgrade major Major version bump. (ex: Chromium 88 to 89) Chromium/upgrade minor Minor version bump. (ex: Chromium 88.0.0.1 to 88.0.0.2) dev-concern infrastructure OS/Desktop
Projects
None yet
Development

No branches or pull requests

2 participants