On 05.11.2014, at 16:02, Kanstantsin Shautsou <[email protected]> wrote:

>> Depends on the kind of job. I'd rather not have builds than run several 
>> hours and produce tens of GB of output to run whenever someone checks 
>> something in, even though I could. 
> "This may be the case in your particular company, product, or team, but I 
> really doubt it's universal. "

The difference is that I'm not trying to force new UI (that could be done just 
as well in a plugin) on hundreds of thousands of users because I don't want to 
install a trivial plugin that would add it to my installs.

Given how Jenkins works, it's much easier to add something that's not provided 
out of the box than to remove something that is, further tipping the scales 
towards not adding something to core.

So the burden is on you to show that it's necessary or useful for a large 
number users, something you haven't done yet.

> This is because people don't know about certain plugins, because jenkins full 
> of useless plugins that hide from eyes good things.

This is about interest in the feature, not the plugin. If there were any 
interest for the feature, there would be

- (tens of) thousands of installs of the plugin showing it's widely considered 
useful, and/or
- feature requests in Jira for a "Poll SCM" link with many votes and watchers

Neither seems to be the case.

> How much plugins were merged to core in comparison to split?

SSH Slaves is the only plugin bundled with core that wasn't bundled due to 
obvious interest of the project (Translation Assistance) or out of necessity 
(detached plugins and dependencies of bundled plugins). And that was five years 
ago.

I think the Windows Batch tool installer (the Windows equivalent to the Shell 
Script tool installer) was available in a plugin before it was in core. There 
is also an effort to add options from email-ext to the bundled mailer, but I 
don't know its status. Note that the installer is a generic admin only feature 
adding no overhead if you don't use it, and the need for fine-grained control 
over build notification emails is a very common use case as should be obvious 
from the number of installs of email-ext.

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to