Auto-update mechanism

[DennisRippinger]

Last year I and a group of colleagues discovered SEU-as-code and now try to establish it within the company for new projects.

I had some free time and developed an auto-update mechanism for packages used internally. It relies on APIs most software publisher (unknowingly) provide, to discover the available versions. Each night out CI triggers the script which checks against these APIs, updates the build.properties file and publish the update to our internal nexus. Basically a mix of curl, jq, and sed to replace the version.

Would this project be open for such a feature? And if, are there any CI constraints that such a PR should follow?

[lreimer]

Hey Dennis,
as discussed at JavaLand this is an awesome idea. So yes, totally open for such a feature.

Here is what I think:

• if the solution is only one simple script to do the work + the CI server integration then it's probably best to integrate it directly here in this repo
• if the solution is more complex and requires more code, then probably we should create a separate repo for this
• regarding CI server support
  • I think the solution should be flexible enough to support several products
  • e.g. Jenkins, Gitlab, Travis CI
• is your current solution always scanning all packages, or is there a way to specify a list of groupIds and artefacts to scan?