[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Jesse Glick commented on JENKINS-49651 Re: Extend plugin/update center metadata with known incompatibilities JENKINS-41854 is another example (DynamicContext needed a workflow-cps update to be interpreted). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188578.1519137284000.20060.1563963180309%40Atlassian.JIRA.
[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49651 Extend plugin/update center metadata with known incompatibilities Change By: R. Tyler Croy Labels: api essentials update-center Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title
Christoph Obexer edited a comment on JENKINS-49651
Re: Extend plugin/update center metadata with known incompatibilities
{quote}I think we can get away with a simpler system{quote}Sure, I just think that with Requirements and Incompatible-With (aka Conflicts) you almost have everything in place to enable:* Renames* Splits* Merges So I added the RPM documentation links here to save the implementer the time to come up with compatible semantics themselves.Thinking about this some more I think Obsoletes and also handling core updates in the same resolver would net you almost everything. (IIRC KK talked about wanting to update core like the plugins)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Christoph Obexer commented on JENKINS-49651 Re: Extend plugin/update center metadata with known incompatibilities I think we can get away with a simpler system Sure, I just think that with Requirements and Incompatible-With (aka Conflicts) you almost have everything in place to enable: Renames Splits Merges So I added the RPM documentation links here to save the implementer the time to come up with compatible semantics themselves. Thinking about this some more I think Obsoletes and also handling core updates in the same resolver would net you almost everything. (IIRC KK talked about wanting to update core like the plugins) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49651 Extend plugin/update center metadata with known incompatibilities Change By: Jesse Glick Labels: api essentials update-center Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Jesse Glick commented on JENKINS-49651 Re: Extend plugin/update center metadata with known incompatibilities 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) --
[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Christoph Obexer commented on JENKINS-49651 Re: Extend plugin/update center metadata with known incompatibilities Maybe go shopping in the RPM dependency documentation for this: http://rpm.org/user_doc/dependencies.html http://rpm.org/user_doc/more_dependencies.html http://rpm.org/user_doc/boolean_dependencies.html And here is a guide from openSUSE on how to do package splits, merges, renames, ...: https://en.opensuse.org/openSUSE:Package_dependencies#Basic_dependencies Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Jesse Glick commented on JENKINS-49651 Re: Extend plugin/update center metadata with known incompatibilities Another use case: for JEP-200 we added several whitelist entries to core that actually apply to classes bundled in plugins, to make sure people could do a core upgrade without having to know about plugins to update. With this API, once the plugin releases appear which (for now redundantly) include those entries, we could delete them from core with a notice that the newer core versions are incompatible with the older plugin versions. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49651 Extend plugin/update center metadata with known incompatibilities Change By: Jesse Glick Summary: Extend plugin/ update center metadata with known incompatibilities Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
