-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Bazel CI: deleting maven_jar broke downstream projects with bazel@head #10322
Comments
It looks like deleting maven_jar != flipping the incompatible change flag, and has a much wider impact that then downstream tests I did in #10090 and https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1251#4a75bdb5-0eba-494a-afaa-39b6f3112c7b I'll see what I can do, especially on the migration tooling front. |
Any updates? |
Yes:
|
All of the known failures have been migrated. Will wait for tonight's downstream to confirm. |
Awesome @jin , thank you! |
The remaining failures are not maven_jar related. https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1306 |
I found the removal of maven_jar also breaks https://github.com/bazelbuild/tools_android, which we use to build firebase android apps. Is the tools_android repo still maintained?
|
Never mind. I found these changes that fix the issue. Cool. |
Deleting the deprecated maven_jar rule broke several Bazel CI downstream projects we build with Bazel@HEAD. (These projects were apparently not migrated.)
Context: #10237
Examples:
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1294#cbe4d084-810d-4349-aedd-a938fbcbf8b2
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1294#1210713f-262e-4363-a30c-f4dcd14d7d00
Unfortunately it's not easy to roll back the culprit commit (88126f8), because two others (6884507, 87da3f6) are built on it, and apparently the rollback isn't clean.
The text was updated successfully, but these errors were encountered: