You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have setup an application in Crowd to connect my Jenkins master 1. Works great.
Now I have setup another Jenkins master 2 and also want to connect it to Crowd. Can I reuse / share the same application here?
I have tested and it seems to work. Probably because I did not enable the SSO part in the application.
Is this an anti-pattern even though it works?
And pros and cons for doing so?
No, your two Jenkins are differenct services. You'll be able to re-use, as in copy, almost all the config and have them behave the same (in Crowd terms), but you can't have one application pointing to many applications
I was assuming, because the two Jenkins are different services, that it would not work. But actually using the same application (not a copy of it) works.
Probably it works in my special case, because the application is actually not pointing to the services. The only part where they would point to the service, is the SSO ACS URL and Entity ID. But as I don't use it, there is no pointer.
Where would it break in my use case?