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
Run gclient verify
in CI before gclient sync
, fix existing violations
#113052
Labels
P2
Important issues not at the top of the work list
team-infra
Owned by Infrastructure team
triaged-infra
Triaged by Infrastructure team
Comments
8 tasks
This should be combined with the effort to stop pulling directly from GitHub. |
This is the bug tracking mirrors for reference: #110142 |
Remaining violations:
|
8 tasks
Today's violations:
|
ricardoamador
added
P2
Important issues not at the top of the work list
triaged-infra
Triaged by Infrastructure team
labels
Aug 23, 2023
harryterkelsen
pushed a commit
to flutter/engine
that referenced
this issue
Oct 23, 2023
cc @sealesj working on mirrors and allowed_hosts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P2
Important issues not at the top of the work list
team-infra
Owned by Infrastructure team
triaged-infra
Triaged by Infrastructure team
Discovered during flutter/engine#36634 (comment), running
gclient verify
reports many violations, including that some of the engine DEPS hosts are not inallowed_hosts
. Fix all existing violations, and update scripts to rungclient verify
in CI beforesync
to prevent future violations from slipping in.The text was updated successfully, but these errors were encountered: