Source control (or version control) is the practice of tracking and managing changes to code. Source control management (SCM) systems provide a running history of code development and help to resolve conflicts when merging contributions from multiple sources.
Hi Community,
Play the new video on InterSystems Developers YouTube:
I'm testing git-source-control and I have problem with a CSP application.
I was able to configure in settings a CSP application that use the path /csp/myapp, that worked.
I have another application /slg and I'm unable to add it to Git.
I created the mapping as "/CSP/" - "/slg" - "csp/slg/", then in Studio when I right click on the CSP folder in the Namespace Work Area, select Git -> Add:
porting new version of .slg to E:\git\iris-prod
No mapping with a matching coverage found for file E:/git/iris-prod
No mapping with a matching path found for file E:/git/iris-prodI am trying to use git-source-control with IRIS.
Hi All! For those of you who are users of our cloud services, you may have been introduced to Health Connect Cloud. One topic within that cloud service that can be a little tricky is understanding how GitLab and the source control workflow fit seamlessly into your integration workflow in Health Connect Cloud. I recently presented a lightboard video explaining how this works, including the slightly different workflows for building interfaces via code versus building via the Management Portal UI. If you use Health Connect Cloud, let me know if this is helpful or if you have questions!
Hi Community,
Watch this video to learn how to leverage embedded (server-side) source control in a build pipeline using the git- source-control package and other additional tools:
⏯ Embedded Source Control with Git & Containers @ Global Summit 2023
The VS Code extension for Deltanji source control has been updated to version 1.2.3. View the change log here for a full list of updates: https://bit.ly/3PqMJ26
Users can now benefit from the VS Code Quick Diff feature when using the ObjectScript extension. To use this feature just click on the gutter decorations to reveal an inline diff experience, where you can contribute contextual commands. You just need to provide VS Code with the original contes of any given file.
Find out more about the Quick Diff feature here > https://bit.ly/46iEnRg
We have some custom tools that do project based deployment from environment to environment. In VS Code, we're struggling to find the best way to export PRJ files that contain the contents of a project the way we were able to in Studio. We can edit existing projects, and in server side editing we can create projects, but we can't seem to extract the project files (Not the classes, the wrapper) to store in our source control solution for deployment purposes.
This question originally appeared in the comments of the article: Git for Shared Development Environments
Looking for advice on best practise (or at least reasonable approaches) for handling the Production class when utilising source control. (And perhaps wider advice around deployment.)
Deltanji 7.1 is now available.
Key updates include:
* Interoperability Production component driver included, for customers who have purchased the add-on. You can watch a short demo of it here.
* Implement multi-select delete of objects and components
* Add setting to give a passable Beyond Compare launch command line
* Support simplified Locations & Routes diagram
For more information, read the release notes here >> https://bit.ly/3mHyJHc
Please get in touch with support@georgejames.com for your release kit.
The update is also available for Serenji debugger users on VS Code, which has the Deltanji solo edition embedded. Simply update the Serenji extension to version 3.2.3 or later and load the server-side code.
Git stores complete history - meaning you would never lose your files, even if they are deleted, they are still available. That, however, presents an issue if large or sensitive files have been committed. Deleting them DOES NOT remove them from history. Recently one of the repos I work on became unexpectedly large, so here's how you can resolve that:
Hi Developers!
As you know InterSystems IRIS Interoperability solutions contain different elements of the solution, such as: production, business rule, business process, data transformation, record mapper. And sometimes we can create and modify these elements with UI tools. And of course we need a handy and robust way to source-control the changes made with UI tools.
For a long time this was a manual (export class, element, global, etc) or cumbersome settings procedure, so the saved time with source-control UI automation was competing with lost time to setup and maintain the settings.
In the vast and varied SQL database market, InterSystems IRIS stands out as a platform that goes way beyond just SQL, offering a seamless multimodel experience and supporting a rich set of development paradigms. Especially the advanced Object-Relational engine has helped organizations use the best-fit development approach for each facet of their data-intensive workloads, for example ingesting data through Objects and simultaneously querying it through SQL. Persistent Classes correspond to SQL tables, their properties to table columns and business logic is easily accessed using User-Defined
Hi Developers,
Often we create and edit InterSystems IRIS Interoperability solutions via a set of UI tools that is provided with IRIS. But it is sometimes difficult to setup the development environment to handle changes we make in the UI to source control.
This video illustrates how git-source-control helps with source control Interoperability components while changing it in the UI.
⏯ Git Source Control for InterSystems IRIS Interoperability with Docker and VSCode
In a healthcare setting we've an Ensemble namespace through which passes a key HL7 feed (the ADT feed from our PAS). It is split up, transformed and passed on to multiple downstream systems. We consider the feed going to each downstream system an interface. Each interface is developed as separately as possible - typically as a separate branch of our git repo (which we access via VS Code).
Community webinars are back!
And we're thrilled to invite you to the webinar of George James Software, partners of InterSystems:
👉 "Demo of Deltanji: source control tailored for InterSystems IRIS" 👈
Join this webinar to learn how the Deltanji source control can seamlessly integrate into your development lifecycle and see a demonstration.
🗓️ Date & Time: Thursday, February 23, 4 pm GMT | 5 pm CET | 11 am ET
How source control integrates with your system is imperative in ensuring it works seamlessly behind the scenes without interruption.
Deltanji source control understands the internal workings of InterSystems IRIS and provides a solution that can seamlessly handle its unique needs, with client integrations for VS Code, Studio, Management Portal, and Management Portal Productions.
You can find out more about the benefits of using a source control tailored for InterSystems IRIS at this webinar.
This demo will show how Deltanji goes beyond the traditional CI/CD pipeline, automating the project lifecycle from development through to deployment, making it the perfect source control companion for organizations with continually evolving systems.
🗓 Thursday, February 23rd
⏰ 4 pm GMT | 5 pm CET | 11 am ET
Sign up here > http://bit.ly/40JOaxo
Listen to CEO George James chat with Derek Robinson, host of the InterSystems DataPoints podcast talk about source control, developer tools and how our solutions are beneficial for InterSystems IRIS users.
In this short 17 minute episode, George and Derek discuss our work with developer tools, and how choosing the right source control can provide users with a seamless solution - which is why Deltanji is seen as the go-to source control for InterSystems IRIS users.
Listen now on the InterSystems website > https://bit.ly/3Jp5py5
or wherever you get your podcasts - just search for 'InterSystems DataPoints'.
Hey Community,
Enjoy watching the new video on InterSystems Developers YouTube:
I am trying to adjust my VSCode settings.json to make my repository to Server Side Source Control. When Adding "uri" to the settings.json to change the setting but VSCode is telling me that the Property uri is not allowed.
Why is this happening?
In our latest episode of Data Points, I had a conversation with George James, CEO of George James Software, about the importance of source control and developer tools, George James Software's own solutions, and their partnership with InterSystems. Take a listen, and visit https://georgejames.com to learn more about George James Software!
Check out this short demo on the InterSystems Developer YouTube channel showing how the new Production Component Driver can be used for Source Control of Interoperability Productions.
The driver enables highly granular management of interoperability productions with tight integration into the InterSystems IRIS management portal.
⏯ Using Deltanji for Source Control of Interoperability Productions
Thank you to everyone who joined our User Group Session yesterday!
It was great showing off the new Deltanji Production Component driver that facilitates source control of interoperability productions, and we had some really insightful discussions as well.
If you missed out on the session and would like a copy of the recording, feel free to drop me a message.
Hi Community,
Watch the recording of the Second Community Roundtable: "What is the best source control system for development with InterSystems IRIS?"
Some great discussions have been started during this roundtable. We invite you to continue these discussions. in the comments to this post.
Tell us, which source control you use and why – in the comments to this post.
Hi developers!
If you missed our presentation at the InterSystems UK&I Summit and our demo during the Source Control roundtable, but you still want to find out more about source control for Interoperability Productions... there’s another chance to see it at our User Group Session next Thursday, November 3rd at 3pm (GMT).
The new driver enables highly granular management of Interoperability Productions with tight integration into the InterSystems IRIS management management portal.
Sign up via eventbrite here >> https://bit.ly/3yqzfvS
The new production component driver for Deltanji enables highly granular management of InterSystems Interoperability Productions with tight integration into the management portal. We presented it at the InterSystems UK&I summit this week and it received a great reception.
It solves the current pain-point of Interoperability Productions being defined in a single monolithic class definition. Deltanji source control increases the granularity with which items can be managed. Instead of versioning a single class definition containing all the configuration items, this new component driver allows individual configuration items to be managed separately. Each configuration item has its own versioning and revision history and can be checked-out, checked-in, and deployed independently of any other items in the same Production.
Because each configuration item within a production class is managed by Deltanji as a first-class component in its own right, Deltanji provides all the source control, versioning, and workflow capabilities that it provides for any other component.
Watch the below clip to see it in action.
We'll be talking about this new feature in more detail at our User Group Session on November 3rd at 3pm (GMT). Register your attendance on Eventbrite here - https://bit.ly/3yqzfvS
To find out more about Deltanji, visit our website georgejames.com or drop us an email info@georgejames.com
We’ll be hosting our bi-annual virtual User Group Session on Thursday, November 3rdat 3pm (GMT). We will demonstrate the new Production component driver for Deltanji - it enables highly granular management of Interoperability Productions with tight integration into the management portal.
The session is also an opportunity for us to help to problem-solve any issues you're having, and a chance for you to offer your feedback on our tools.
Those interested in finding out more about Deltanji source control are welcome to join us too.
Sign up for free on Eventbrite >> https://bit.ly/3yBVYVO
InterSystems Interoperability Productions are defined in a single monolithic class definition. A production can contain many hundreds or thousands of configuration items. This presents a problem if multiple developers are working on different Business Processes within the same production simultaneously. Simultaneous development is almost inevitable for large productions containing many configuration items.
Hi community members!
I'd like to know about what source control version is recommended to use with Caché / Ensemble. Can someone help me? If yes, there is some documentation to how to configure?
Thanks,
José Sampaio.