Looking for Some Best Practices for Managing Code Repositories in Jazz SCM ??
Hey everyone,
I am currently working on a large--scale project using Jazz SCM,, and I am looking for advice on best practices for managing code repositories effectively. Our team is growing, and we want to ensure we're maintaining a clean, organized,,, and efficient workflow. Specifically, I am interested in ::-
- Strategies for structuring repositories with multiple components.
- Tips for managing branch and merge strategies.
- Recommendations on setting up permissions and access controls.
- Best practices for integrating with other tools, like Jenkins or JIRA.
If anyone has experience with these or any additional tips, I'd love to hear your insights. We're aiming to keep our process streamlined while avoiding common pitfalls,,, so any advice would be greatly appreciated...! I also read this https://jazz.net/forum/questions/207019/is-there-any-standard-process-of-best-practices-for-source-code-management-in-ibm-rtc-flutter but couldn't get any solution related to my query.
Thanks in advance..!
David Miller
One answer
This is a 'how long is a piece of string' question!
There's so many ways you could set this up, but I would always advise to start and keep it as simple as possible. Some very, very general guidelines:
- use your system architecture to define units of release ie. things that you would version and build as a single whole 'thing' that would then end up part of your system, These would be set up as components
- use a component for your overall build and deploy scripts, and your integration/system test scripts
- create streams for development of each major piece
- create an integration stream where you bring together baselines of all the pieces to form the system
Where are you based? I would be happy to have a one on one discussion with you if you'd like to give you some ideas to start with.