a month ago
Hi,
I configured gCTS with a GitLab repository in an SAP S/4HANA 2025 environment. While commits work correctly upon releasing the transports, I have encountered an issue with the 'Push Objects' functionality during synchronous execution.
Debugging the point of failure reveals that the exception occurs because the system cannot identify the API user.
Comparing this method with gCTS in S/4HANA 2023, I noticed that the API object is only instantiated when using GitHub. Since I am using GitLab, the code to retrieve the API object is bypassed, which is why 'Synchronous Push Object' works correctly in that version.
Is anyone else experiencing this error using gCTS on S/4HANA 2025 + GitLab during a 'Synchronous Push Object'? If you're using gCTS on S/4HANA 2025 +GitHub instead, I’d appreciate your feedback to confirm if the functionality works in that setup.
Thank you,
Alfonso.
Request clarification before answering.
Hi,
After reporting the issue to SAP, they have released an SAP Note to fix it.
3714602 - gCTS ABAP: Fix authentication error for Gitlab repositories
The note has also been included in:
3378978 - gCTS: Collection of Corrections to Known Issues
2821718 - Central Note for Git-enabled Change and Transport System (gCTS)
Regards,
Alfonso.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 11 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.