Hello,
we are intensely prototyping gCTS to learn about the pros and cons and especially the differences to abapGIT. Also very familiar with the non-ABAP world.
One outcome is, that gCTS behaves very obstinately when it recognizes only portions of an object to be registered by a transport. As an example: only a method has been tracked by the transport, but not the hole class. This situation is quite normal, when code exists, and developers do maintenance only. gCTS stops then committing this transport. Sounds safe-guarding, but in fact it produces a lot of efforts and down sides.
Solution now would be, add the underling code base to the repro by a transport, then each delta will be handled correct by gCTS.
But think twice, it will mean, that at the end nearby the hole code base, including SAP and 3rd party code need to be added. And all this manually, by someone.
Is this the concept?
Better way would be to improve gCTS, like adding missing parts of an object automatically. Sure, this way you do not get the complete code base under GIT control, but this is not the target.
Target is, to get all transports committed smoothly without user interaction.
What do you think?
There would be more to say, about how the GIT concept has been transferred to the ABAP world, but this will be another story. 🙂
Many thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.