Hi Eduard! thank you for this series. It has been very useful for understanding how to structure GitLab-based CI/CD around InterSystems environments.

I’m trying to adapt the CD approach from this post to InterSystems IRIS 2025.1 on Windows, and I’ve been running into some trouble with the command-line execution side. In particular, I noticed the article’s examples are centered around Caché/Linux-style usage, with the note for IRIS and Windows. In my case, I can execute my routine interactively through the terminal path, but when I try to use run / runw from a GitLab Runner using the Shell executor, the process completes differently and the code does not appear to execute as expected.

Have you seen this behavior before on Windows with IRIS? Is there a different command you would recommend today for IRIS 2025.1 on Windows in a GitLab CD script, especially for non-interactive execution from a runner?

Also, have you ever implemented CD using functionality from the Embedded Git package from Open Exchange instead of a pure import/load approach? For example, something conceptually similar to calling an Embedded Git API method from a CI/CD job so the server pulls the approved code from the repository.

Any guidance on the recommended command or pattern for modern IRIS on Windows would be greatly appreciated. Thanks again for putting this series together.