How does this tool interleave with version updates? What if the package requires plugin A, version 2.0 and plugin B, version 3.0. Plugin A, version 2.0 requires a minimum Jenkins version of 2.x but plugin B, version 3.0 does not work with Jenkins version 2.x?
This has a couple of solutions I can think of: 1) The team supporting a package has to release a new version of the package for new versions of Jenkins itself. I suppose it could be required for every LTS version or the package would be marked unsupported for the Jenkins version. 2) The package could supply minimum and maximum plugin versions that all work together no matter which combination of versions are loaded. Or, similarly, there could be a list of acceptable versions for each plugin. This would be easier to think about if I knew more about the way Jenkins decides which versions of plugins are offered for loading in Manage Jenkins > Manage Plugins. Perhaps it could cooperate with the On Tue, Mar 17, 2020 at 12:30 PM Sladyn Nunes <[email protected]> wrote: > I was discussing with @FelixQueiruga on the UX Sig channel regarding reuse > of the jenkins core to generate the forms for the UI for each plugin but I > guess that option is not very viable, since it would prevent update to the > forms and any such update would bring down our distribution service, we > therefore currently stand with the option to generate the fields using the > json schema that JCasC uses but that is not very reliable. I was wondering > if we could scan all the DataBound Constructors and generate as many fields > as we can, but I guess that is too much overhead. I would love to get some > thoughts on this. Feel free to add your reply here or in the docs. > The link to this section in the proposal is here : > https://docs.google.com/document/d/1C7VQJ92Yhr0KRDcNVHYxn4ri7OL9IGZmgxY6UFON6-g/edit?disco=AAAAJMf0sg0 > > Thanks and Cheers > Sladyn > > On Wednesday, January 8, 2020 at 8:19:32 PM UTC+5:30, Rick wrote: >> >> Hi team, >> >> I'd like to share an idea with you. There are some original discussions >> from the GSoC thread >> <https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/36332f60-e8f0-4cc0-a37d-642990c824d9%40googlegroups.com?utm_medium=email&utm_source=footer> >> here. >> >> For many users, they download Jenkins first, then select some plugins and >> config them. It might take a lot of time, like hours. But if we can get a >> perfect Jenkins distribution which contains all we need, it can save that >> time for us. Yes, I propose an out of the box solution. >> >> The service could be like this, a website offered as >> https://customize.jenkins.io. Plus, it should be self-host. People can >> select the following configurations: >> >> - Jenkins core version >> - plugins >> - common configuration, user/password, update-center site e.g. >> - plugin based configuration, Kubernetes, Sonarqube plugin config e.g. >> - multi-form package, jenkins.war or docker image >> - other things >> >> Two projects are expected backend and frontend. I think >> https://github.com/jenkinsci/custom-war-packager already did a lot of >> works. We can reuse it in this project. The backend should provide the >> modern Restful API. We can start the backend project with SpringBoot, it >> can save a lot of time. >> >> About the frontend project, I don't have too many experiences on it. For >> example, we can start it by React framework. If you're instrested in it, >> please help to add more ideas on it. >> >> Any feedbacks are very appreciated. >> >> Best regards, >> Rick >> -- >> Zhao Xiaojie (Rick) >> Blog: https://github.com/LinuxSuRen >> Twitter: https://twitter.com/suren69811254 >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/34c9dbcc-086d-45f5-b372-89367114ce6c%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/34c9dbcc-086d-45f5-b372-89367114ce6c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAA4vtDRmMLrrVSPypcYowFJZyNm7sgK5VeF76NiL_VRzJKFiuw%40mail.gmail.com.
