| Yes Linux package manager docs would be a good source of potential use cases to validate a solution against. I think we can get away with a simpler system, since:
- Jenkins does not really need to deal with platform-specific issues.
- Most plugin development happens under a single organization’s umbrella. Even if plugin maintainers operate autonomously they are still delivering software targeted toward a core produced by that same organization and using tools and an update center maintained by the same core developers. This is a much simpler situation than Linux, in which both the kernel and various userspace software projects are maintained by completely disparate groups, and multiple distributions compete to package those components independently, picking versions and backports, with these decisions often being made by people other than the upstream developer.
- Evergreen reduces the pressure to support exotic scenarios that might occur with people running the many LTS flavors offered by various Linux distributions. The Jenkins project produces only one official “long-term” support line, and (until Evergreen) no “pinned” plugin versioning at all.
|
