cancel
Showing results for 
Search instead for 
Did you mean: 

Single central repository - good practice?

Former Member
0 Kudos

Is it a good practice to use a SINGLE central repository for ALL projects in a company?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello

There is no right or wrong on this.  In a small organisation, a single central repository could work.  If you have totally separate projects, you could configure a central repository for each project.  The number of local and central repositories can be configured to whatever suits.

Personally, I NEVER use central repositories to promote code, I only use them within the development environment. I always use ATL (packaged with DDL, etc.); it is quicker, less error prone, and more secure.

Michael

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Eugeniy,

it is not a best practice to use a SINGLE central repo.

Usually you would use a three tiered landscape with dev, test and prod repo.

For further information you can refer to this blog post

Former Member
0 Kudos

Hello Eduard,

thank you for your reply,

but actually the question is not about three tiered landscape, there are no doubts that it is a good thing.

I would like to know if it is a good solution to have jobs, dataflows etc. from different, not connected with each other projects in the same central repository? Or is it better to have a separate set (dev, test, prd) of central repositories for each project?