Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Multi-tenant deployments using Cloud Manager?

Avatar

Avatar
Level 1
geetikac6373881
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
geetikac6373881
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
geetikac6373881
Level 1

27-05-2020

Hi Team,

 

One of our clients is looking to get onboard to Cloud Manager and they have multiple sites running on the same instance. All of these sites are having their own repositories and their own pipelines in a lower environment. Since we get only one Git repo when we move to Cloud manager and limited set of pipelines, is there a way that we can move to the cloud manager and could support multiple git repos and multiple pipelines for the sites?

 

Looking for some insights if someone in the community has come across the same usecase?

 

Thanks,

Geetika

View Entire Topic

Avatar

Avatar
Give Back 5
Level 4
SameerBhalerao
Level 4

Likes

35 likes

Total Posts

30 posts

Correct Reply

16 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 5
Boost 3
View profile

Avatar
Give Back 5
Level 4
SameerBhalerao
Level 4

Likes

35 likes

Total Posts

30 posts

Correct Reply

16 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 5
Boost 3
View profile
SameerBhalerao
Level 4

01-06-2020

Hello,

 

This scenario is coming up often now.

 

Cloud manager allows multiple code quality pipelines but only one deployment pipeline which promotes the code till prod deployment with several steps including checks and approvals from CSE.

 

I think two options are there with a bit of restrictions and varying degree of effort:

1. Create separate branches (you can call them long running feature branches) and map them to the deployment pipeline when required. You can keep promoting or cancel the pipeline in dev or stage to allow other pipe lines to be allowed for deployment. It assumes you have a good gatekeeper and good quality control practices so that one site does not write/update others etc. This is simple to do but has a lot of operational effort and involvement of cloudmanager gatekeeper.

2. Have a local master repo where the local repos can sync the codebases. Once deployment to AMS environment is needed, you need to sync it to cloud manager git using jenkins hooks. So ideally use cloudmanager as code promotion for QA, UAT only on need basis and not a day to day code push. This solution will work but need effort in terms of setting up some infra and processes initially.

 

 

Thanks!