Switched to Node test runner sharding as well in GitHub - it's faster.
run: node --test --test-shard=${{ matrix.shard }}/${{ strategy.job-total }}

Haven't seen such feature - we are using SAP Cloud TM service, just to clarify.

locally, then GH on PR / merge - so you always see the tests state in GH. Build / deploy goes via SAP CICD (DEV) after merge. Then we have as well a dedicated release script which generates stuff, tags, publishes etc. and also via SAP CICD builds / deploy but this time with SAP TMS.

I was not digging into sharding with cds test. But would be interesting to check it in GitHub Actions. SAP CICD is not an option AFAIK, as you can't pass index/number of shards anyhow and for the stage only one container is given.

It's this one: community.sap.com/t5/technolog..., updated the article.

And your homophobic cancer has finally reached this place.

And, of course, Gartner is here with their "magic".

Definitely 👇

I just started with Copilot, on-premise system, let's see..

There are techniques which can be applied for any DB, I hope to write about it one day.

"In the next episodes, we will see how to address this." I hope.