gCTS on SteamPunk, pulling by Commit ID does not work

[aoyang]

Hi, we are using gCTS on SteamPunk(BTP ABAP Environment) and we have Dev and Qas environment. Pushing from Dev to remote repo and pulling them into Qas works if we are pulling all the released transport requests with 'Latest' option.

But we want to pull specific transport request to Qas. There is an 'Commit ID' option when pulling in Qas, which only pulls the specified Commit ID, which seems to serve this purpose. However, it only works if the commit ID of transport request specified is the earliest(oldest) on the timestamp.

To elaborate:

In Qas, press Pull and specify Commit ID(12345) of transport AAA. -> Only transport AAA is imported to Qas(Expected result).

In Qas, press Pull and specify Commit ID(67890) of transport BBB. -> Both AAA and BBB are imported to Qas(Unexpected result).

- Transport AAA, Commit ID 12345, pushed at 10:00:00 from Dev

- Transport BBB, Commit ID 67890, pushed at 11:00:00 from Dev

Is this the expected behavior? It seems that like all the transports that are older than the chosen Commit ID are imported, which I feel like is inconvenient and beats the purpose of this function.

I tried with both short and long commit ID, and using tag but it ended up in the same result.

[former_member245527 · Accepted solution]

Hello Aocheng,

Thank you for this question! The behavior you describe is indeed also the expected behavior. As of today, in the Manage Software Components Fiori App or the MANAGE_GIT_REPOSITORY Web API, there are the following three options for pulling commits (= transport requests):

1. "Latest" - pulls all commits up to the last remotely available commit
2. "Commit ID" - pulls all commits up to the specified commit. There is no distinction whether the user enters the short or long commit ID.
3. "Tag" - pulls all commits up to the commit that is referenced with a uniquely named tag

Important: With all three options, the commit, including the branch's complete history (up to precisely this commit), will be pulled.

I assume the function you are referring to is the git cherry-picking mechanism. This feature is not available in SAP BTP ABAP Environment, a.k.a. Steampunk. For completeness, here is the link to the official documentation.

Best regards

Henrik