-
Notifications
You must be signed in to change notification settings - Fork 15
Switch Renovate to opt‑out mode (#245) #118
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,19 +5,31 @@ | |
| // Commit author | ||
| gitAuthor: "eclipse-score-bot <score-bot@eclipse.org>", | ||
|
|
||
| // Target following repositories | ||
| repositories: [ | ||
| "eclipse-score/bazel_cpp_toolchains", | ||
| "eclipse-score/devcontainer", | ||
| "eclipse-score/docs-as-code", | ||
| "eclipse-score/inc_someip_gateway", | ||
| "eclipse-score/itf", | ||
| "eclipse-score/os_images", | ||
| "eclipse-score/qnx_unit_tests", | ||
| "eclipse-score/rules_imagefs", | ||
| "eclipse-score/score", | ||
| "eclipse-score/testing_tools", | ||
| "eclipse-score/toolchains_rust", | ||
| // Autodiscover repositories in the org and opt-out where needed. | ||
| autodiscover: true, | ||
| autodiscoverFilter: [ | ||
| "eclipse-score/*", | ||
| // Explicitly exclude archived repositories. | ||
| "!eclipse-score/inc_feo", | ||
| "!eclipse-score/inc_mw_com", | ||
| "!eclipse-score/inc_mw_log", | ||
| "!eclipse-score/examples", | ||
| "!eclipse-score/inc_process_test_management", | ||
| "!eclipse-score/inc_process_variant_management", | ||
| "!eclipse-score/operating_system", | ||
| "!eclipse-score/inc_json", | ||
| "!eclipse-score/inc_config_management", | ||
| "!eclipse-score/test_integration", | ||
| "!eclipse-score/test_module_a", | ||
| "!eclipse-score/test_module_b", | ||
| "!eclipse-score/inc_abi_compatible_datatypes", | ||
| "!eclipse-score/inc_ai_platform", | ||
| "!eclipse-score/inc_gen_ai", | ||
| "!eclipse-score/inc_score_codegen", | ||
| // --- Self-referential: exclude the renovate config repo itself --- | ||
| "!eclipse-score/cicd-workflows", | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What would happen, if this line is removed? I expect that we still want to get updates for Github Actions used within this repository.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. renovate is only updating score bazel modules. So its irrelevant here at the moment, |
||
| // --- Active repos intentionally opted out --- | ||
| // (none yet — add here when needed) | ||
| ], | ||
|
|
||
| prFooter: "This PR was generated by [#infrastructure](https://github.com/orgs/eclipse-score/discussions/107) automation. Contact us if you have any questions or feedback.", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just realized there was a problem running it in more repos. It requires valid and complete lockfiles. Those don't work in all repos. Our current lockfile check does not verify completeness.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing out the lockfile completeness issue. Since we’re moving to opt‑out, would you recommend we add a stricter lockfile validation step before enabling Renovate, or should we exclude repos without complete lockfiles for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AlexanderLanin Just following up on my earlier note about lockfile completeness. Since we’re moving to opt‑out, I wanted to confirm the best approach:
Should we add a stricter lockfile validation step before enabling Renovate across repos?
Or would you prefer we exclude repos without complete lockfiles for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Subramanian-K812 I've added it to the infrastructure meeting agenda. In the meantime I'm trying to generate an overview of the current state.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not promising.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That seems weird though no? Didn't Dan add module lock error file stuff in many repos?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated/fixed metrics at https://eclipse-score.github.io/.github/#tech-stack