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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello all
I have question about architecture o CI/CD proces using JIRA Servicedesk, JIRA Software, Bitbucket, Bamboo and Crowd for managing users.
Because our Servidesk is shared at internet we have JIRA SD and SW in DMZ and Bitbucket, Bamboo, Crowd in LAN - all these are separated vLans, where traffic should be close for all to LAN without AD to Crowd connection.
If You have better ideas for architecture please write. What is best architecture for that in You opinion :)
Thanks in advance
Maciej
The setup you describe makes sense, putting the public-facing Jira applications in the DMZ so that they can be accessed on the Internet and the rest of the applications on the internal LAN since only internal users access them.
Do you have a way to open a port from the LAN to the DMZ for the option of connecting the applications with application links or in case you want to use Crowd for User Management of Jira?
Hello Ann,
Management users is via Crowd witch is in the separated vLAN (Bamboo, Bitbucket and Crowd) the second vLAN (DMZ) is for JIRA and Confluence.
Problem is how to CI/CD proces should be setup where we need automatic deployment to LAN (ports are not open)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.