on 01-02-2022 12:42 PM
Hi Gurus,
I am going to use the gCTS application for TR and ultimately CI/CD purpose. We are going to have a 4 environment landscape. below are few queries that I have, can you please provide some clarity.
1. What is the best way to set up the github repository? Should we use 2 branch structure or 4 branch structure for prod and non-prod(3) environment?
2. If we use 2 branch structure, one for non-prod and one for prod. When we release the TR in dev it performs the commit in Github repository. Does this mean that the code is updated in all the non-prod environments ? Or the code is only updated when pulled to the specific environment ?
3. Conflict resolution requires, setting auto push and pull set to false. If we implement this feature then does this mean automatic CI/CD won't be possible ? If its still feasible to do automation then how its impacted if conflict resolution is selected.
4. Through Fiori gCTS app if we activate an old commit in ACC environment will this make that commit activated in DEV and non-Prod environment also, in case we have the same branch active in all environments?
Thanks,
Sonal Saurabh
Hi Sonal,
let me try to give some hints.
1. there is no single way to go for branch design. One thing should in any case be that the production system relies on an own branch - could be 'main' or maybe 'release' or whatever you would like to name it. Another aspect of branch design is how you would like to handle maintenance. Will you have a separate maintenance landscape? How and when would you need to do maintenance? How and when shall fixes be integrated into new development? that are some aspects in here.
2. gCTS will never import anything automatically into any system. If two systems have the same branch of a repository as the active one, this only means that the same commits are visible. You will activate the commit in any system that is not the pushing one whenever it suits you by executing a pull.
3. Conflict resolution (and disabling automatic push and pull) is not a feature that you implement. There these two parameters that can be set per system per repository. You would only set these parameters in systems and for repositories where you develop something and where changes from different sources are pushed to the same repository.
4. as in 2: activation of a certain commit is done system specific. This is an import activity into the ABAP runtime that has to be triggered individually per system. Each system can have a different commit of a branch as the active one.
Kind regards
karin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.