What are the reasons behind this being implemented in the commercial editions only ? and why don’t you want to make it configurable for the commercial editions, so that the customers themselves can decide if they want to “stick” to the old way of installing plugins or the new manual (and very very time consuming) way via for example a startup property ?
You implement a “force” mechanism without asking the customers of the commercials editions if this should be configurable and I don’t get why this manual installation should “only” be for commercial editions. It’s a “one-size-fits-all” (one size fits nothing as I tend to say) approach - where you decide what’s best for customers. That’s a no-go
In our company I am the person in charge of the update of SonarQube – another person is in charge of the plugin updates and all the UI settings (rulesets, portfolios etc). The other person do not have access to the filesystem, so on every update of a plugin or when adding new plugins the other person needs to have me to work. (Dev and Ops seperation right ) - that’s a really annoying extra process. Think about if Atlassian did this on their Jira, Confluence and Bitbucket products without asking the customers… It’s the first product ever where I see this approach on the plugin eco-system. Give the power to the people and remove the force mechanism in the commercial editions via the possible to configure this as a system startup property. Thanks.
When I need to update to the new manual way of installing plugins I need to find all the “download urls” for the plugins and put them into our Ansible configs. It’s really a “headache” for us in our company.
So once more (also asked to our account manager): Why don’t you want to make it configurable for the commercial editions (like the community editions), so that the customers themselves can decide if they want to “stick” to the old way of installing plugins or the new manual (and very very time consuming) way. I haven’t found that answer in the supplied information.