Introduce EOL notifications to the spring boot gradle and maven plugins #45043
Labels
for: team-meeting
An issue we'd like to discuss as a team to make progress
status: waiting-for-triage
An issue we've not yet triaged
Given the pace of development in the spring projects, and the EOL support polices, it is hard for developers to know if they are using an EOL library in thier application. The maven spring boot and gradle plugins should warn developers if they are building a spring boot apps that is using EOL libraries.
When invoking the gradle and maven plugins, the plugin checks the version number of every jar under the
org.springframework
group ids to produce a report showing which jars are EOL but are in commercial support, which jars are beyond commercial support windows. If a jars is within 4 weeks of OSS EOL a warning should be included in the report. The report should be printed to the console.The plugin can have warn and enforce modes, with the default being warn. In warn mode, the plugin simply prints out a report, in enforce mode the plugin fails the build.
For large organizations with mature Platform Engineering teams looking to aggregate these warning centrally, the plugins should offer an option to centrally configure the behaviour of the plugin.
SPRING_BOOT_EOL_WEBHOOK
environment variable so that it can be turned on by platform engineering teams.SPRING_BOOT_EOL_MODE
which can have a value ofenforce
orwarn
based on this value the plugin can fail the build or not.The enhancements proposed by the issue are very helpful for large organizations with central platform engineering teams looking to put guardrails in place to enforce dependency upgrades or nudge developers to upgrade in a timely fashion.
The text was updated successfully, but these errors were encountered: