Feature Request: Executing Non-Compile-Dependent Recipes #994
Description
What feature do you want to see added?
Background
I have observed that some plugins are so outdated that they fail to compile, even with JDK 8. These plugins require manual intervention before they can be updated using our tools. However, certain recipes, such as AddCodeOwner and SetupDependabot, do not require successful compilation of the plugin.
Proposal
Would it be beneficial to execute these non-compile-dependent recipes even when a plugin fails to build? Alternatively, should we ensure that a plugin compiles successfully before applying any recipe, regardless of its dependency on the build status?
Considerations
-
Advantages:
- Applying recipes that don't depend on a successful build can speed up modernization efforts and provide immediate value in certain areas, such as code ownership and dependency management.
- It allows us to handle low-hanging fruits without waiting for a full compilation fix, which might be resource-intensive.
-
Challenges:
- Ensuring clarity on which recipes can be safely applied without a successful build.
- Managing potential inconsistencies or issues that might arise from applying recipes in an uncompiled state.
Request for Feedback
I would appreciate input from the team on the feasibility and potential impact of this approach. Should we proceed with executing non-compile-dependent recipes on outdated plugins, or prioritize achieving a compiling state first?
Thank you for considering this request.
Upstream changes
No response
Are you interested in contributing this feature?
No response