Crowd scaling users for Jira and side effects for Jenkins performance or stability?

[Tad Foster]

We are considering adding several hundred thousand users to our production crowd instance to enable non-jira users into a user-picker role on issues (example, Stakeholders) for Jira. Is there any side affects to other tools like Jenkins by adding this volume of users? Currently we have under 1k total users on this Jenkins controller. If we add hundreds of thousands of users to Crowd could it potentially crash our Jenkins server? Ref. https://plugins.jenkins.io/crowd2/

[Craig Castle-Mead · Accepted solution]

Hi @Tad Foster 

I believe the Jenkins Crowd plug-in you’re using only supports “on demand” user provisioning, ie: a user is only created/synced in Jenkins when they successfully authenticate with Crowd, so if you have 100,000 users in Crowd cause you need them as JSD customers, but then have a group that is able to authenticate to the Jenkins app with say 500 users - your MAXIMUM number of users in jenkins would be the 500, and this would only be reached gradually as/if every one of those 500 users authenticated. This means your Jenkins instance won’t have the full 100k users and shouldn’t suffer a performance hit (based on this factor alone). YMMV

[Tad Foster]

Thanks Craig!