>
> So they would simply not install any localization plugin. Great, so
> they're completely irrelevant as far as considering their preferences goes
> (beyond removing translations from everywhere else).


I can imagine a local company which installs a single localization plugin
That's why I lean towards having separate plugins for each locale.

If you install them, you get the newest releases of dependencies anyway,
> unless you do something unsupported with the metadata.
>
Depends on the installation logic implementation, but generally "yes".
Anyway, I would expect Incremental Tools to eventually simplify managing of
aggregator plugins.





On Tue, Aug 28, 2018 at 3:03 PM Daniel Beck <[email protected]> wrote:

>
>
> > On 28. Aug 2018, at 14:54, Oleg Nenashev <[email protected]> wrote:
> >
> > I do not know any organization which actually does that. Usually Jenkins
> is managed via various shared services teams if it gets to such scale, and
> having different localizations makes the system generally unsupportable.
> Imagine you get a support tickets with screenshots in Russian.. oh wait, it
> happens in JIRA sometimes.
>
> So they would simply not install any localization plugin. Great, so
> they're completely irrelevant as far as considering their preferences goes
> (beyond removing translations from everywhere else).
>
> > I do not see a particular need in an aggregator plugin, especially
> taking our experience with maintaining them. For example, the current
> version of Pipeline aggregator just contains obsolete plugins with known
> incompatibilities like JEP-200.
>
>
> Aggregator plugins do not 'contain' anything, they just list a bunch of
> plugins. If you install them, you get the newest releases of dependencies
> anyway, unless you do something unsupported with the metadata.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/jeKVskUwE8M/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/F5F32EE4-66F0-4892-B7CA-50CB386D8318%40beckweb.net
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPfivLBDOdEbz7sGEhAo-cUfTnm0im0yxBwQ5vy1TYRXVA5fBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to