cancel
Showing results for 
Search instead for 
Did you mean: 

gCTS - Pull does not save in TR

07-22-2021 9:30 AM
giulia-felappi Participant
4365 views 17 comments
0 Likes
SAP Managed Tags
Subscribe

Hello everyone,

we recently configured gCTS on our S/4HANA 2020 landscape (DEV/QAS/PRD).

We have a repository on GitHub where we've stored some custom developments, pushed from a different system out of this landscape, also configured with gCTS (sort of a dedicated prototypes system, let's call it DVX).

DVX has this repository registered with role Development.

What we want to achieve is to register our repository with role Provided into DEV system, clone it, pull the changes, and automatically put them in a TR which can be used to transport our objects trough QAS and PRD.

We are able to register and clone the repository, but it seems that no TR is ever created on DEV system.

We are following SAP Help documentation and it seems something that should work, we should expect some TRs named "DVXKxxxxxxxxx".

Has someone encountered this issue?

Thank you
Regards

0 Likes

Accepted Solutions (0)

Answers (7)

Answers (7)

sunil_sap18
Explorer
0 Likes

Thanks giulia.felappi , for a quick response

sunil_sap18
Explorer
0 Likes

Hi giulia.felappi ,

Recently we setup gCTS in SAP systems and facing a similar issue in target system.

Pull is not creating a transport request in target SAP system and none of the objects are imported. I can see all the pull requests in activities tab, but 'Request' column is blank for all pull requests. And as mentioned by karin.spiegel, the corresponding logs also do not have the three additional actions Add_to_buffer, export and import.

Can you please let me know how was this resolved?

Regards,

Sunil

giulia-felappi
Participant
0 Likes

Hi sunil.sap18

we ended up upgrading our S/4HANA landscape to version 2021, then repeated the configuration and everything went well. Might have been a bug that got fixed, unfortunately I'm not sure.

Regards

Karin
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Giulia,

you need to get back in status 'ready' with your repository to make pushes work. Could you please try to get this done by using the 'Update to latest commit' as described in here: https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/202009.002/en-US/be2f23a9d02f4575b9e212...

in addition (or after having the repository back in state 'ready'), you could maybe check this Guided Answer: https://ga.support.sap.com/dtp/viewer/index.html#/tree/2504/actions/34024:40872:40874:39420

Kind regards

Karin

giulia-felappi
Participant
0 Likes

Hello karin.spiegel

repository is now in status READY.

But as you can see from below screenshot, the issue is that none of the pull requests generate a corresponding TR.

The guided answer is about TR release and PUSH activities. We are stuck with the configuration and do not know how to proceed.

Thank you!

Regards

Karin
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Giulia,

could you please let me know what is shown on the Logs tab? Are there any errors?

Thanks and kind regards

Karin

giulia-felappi
Participant
0 Likes

Hi karin.spiegel

here's the log.

Clicking on the first entry (related to my "Update to latest commit") opens the following pop-up, but clicking on any of these logs entries does nothing, nothing else is displayed rather than this.

Thank you!

Regards

Karin
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Giulia,

this looks strange. The log should have three additional actions: Add_to_buffer, export and import

Did you set the parameter VCS_NO_IMPORT for your system or repository? (details in here: https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/202009.002/en-US/99e471efcbee4a0faec82f...)

Does the user DEVELOPER have permissions in your system to create transport requests in STMS?

You can find out easily by using the Health Check in the gCTS App when you are logged on with the user developer. The check Transport Management System should show an error or warning in that case. The details of the check explain what to do

If not, could you please open an incident so that my colleagues from support could take a look into your system? Please provide them directly with the information that these steps are missing in the log

Kind regards

Karin

giulia-felappi
Participant
0 Likes

taranam We did exactly as you say, the point is that the final step doesn't work. No TR is created in any queue, nor in the gCTS Fiori app (see my previous screenshot).

taranam
Contributor
0 Likes

Can you check Logs tab once .. then it should show some warning /error there .

Like in my case its all sucess in Log

giulia-felappi
Participant
0 Likes

taranam

this is what we have.

taranam
Contributor
0 Likes

Few actions are missing like IMPORT .. Try doing RESET once . On top right side close to Clone Repository we have reset button click on that..It might work for commits that are present .. We also faced this issue but in our case we upgraded kernel of QAL system to ensure supported tp and R3trans version available.. So you can check the kernel version once for both systems and see if target requires upgrade.

taranam
Contributor
0 Likes

This is how it will look like - in my case G20 is my vsid

taranam
Contributor
0 Likes

In Commits Tab under Action ; your pull is enabled . Click on Pull button in front of your TR then the Pull will get disabled and TR should be available

giulia-felappi
Participant
0 Likes

This does not do anything unfortunately. I've clicked on Pull on multiple Commits, but the system only says "System was set to commit xxxxx". No TRs are visible in the import queues.

taranam
Contributor
0 Likes

In the target system TR is imported with name as vSID** example if you gave VSID in repository as GEV then TR in your QAL system will be like GEV******. .Also you need to manually commit in QAL system for transport to be imported unless you are using pipelines . Goto your repository in say QAL system , go to Commit tab and you will see the commit ids --- on right side of commit id you have 2 buttons . click on first one (Pull) ..

This will import the TR into system .I hope you are able to see commit ids in commit tab if the set up is right

giulia-felappi
Participant
0 Likes

Hello taranam

you're right, vSID is named "GIT" in DEV system.

So TR should be named GITKxxxxx.

But apart from this detail, TRs are not created in the first place. Am I missing something?

Thank you!