InterSystems’ team is heading to the IC HACK ‘25 hackathon, taking place on February 1-2, 2025 in London, UK.

IC HACK ‘25 is an annual hackathon organised by Imperial College London Department of Computing Society. It is the biggest student-run hackathon in Europe, where over 700 of the UK's most creative and talented students work together for 24 hours of learning, building, fun, and networking.

Hello everyone! This is my first post into the developer community and one that I hope is fairly simple to answer. In our environment we currently have 3 different Test environments for testing before migrating code to our Prod environment. Currently we are working on establishing a source control method using Git in house which has been a bit of a struggle. We have also had developers that had used different test and migration methods in the past which has caused some issues with keeping the different test environment in sync.

What I am looking for is an option to either copy a whole Namespace/Production from either the CRT environment or DEV environment to our INT environment for integrated testing. Currently the process that we use for code migration between environments is by using the Studio export and import method on projects that are created in Studio. Would that same approach be used to copy the whole Production and contained classes and Business services, Processes, and Operations? Should we use the Deployment Changes method under Interoperability in the Management Portal, and if we use this approach, if we are wanting to overwrite the productions that are currently in the INT environment with updated production components and code would we include the production classes and PTD files?

What I would like to be able to do is copy an entire Namespace/settings within registries over and overwrite the current data/settings with one from the higher test environment if possible.

Ultimately since we are migrating to GIT and VSCode, what approach would be useful in pulling down from a repo that we use?