https://www.youtube.com/embed/G93HBywyaSY [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
I am using Atelier + EGit plugins for a project. Is it possible to turn the storage definition off in Atelier so this does not get copied to Git when I make changes? While developing on different versions of the code on different systems, it may cause conflicts and excess noise in the source control history
It's been a while since I've posted about Embedded Git on the Developer Community, and I'd like to provide an update on the massive amount of work we've done this year and where we're going next.
Context
If you're building solutions on IRIS and want to use Git, that's great! Just use VSCode with a local git repo and push your changes out to the server - it's that easy.
Hi everyone, I am new to "git-source-control", what i am doing so far will explain you in few steps. 1. installed git-source-control into a namsapace TEST using ZPM "install git-source-control" 2. configure the git settings and created a new mapping for as such
I was wondering if there was a way to if the user is using Studio and changes a file to get the users name and have a function run when the file is changed.
Ive got this working for .int files but not for .csp or .js or .css or any other kinds of files.
When we edit code we are logged in to the Cache backend’s server through Studio by using an iPaddress (which is on our network).
I know now there are concepts of file locks and logs for when certain tasks are ran or when a user maybe edits a file
I'm using Git with DeepSee and when I need to do a commit to the git repo I'm exporting ALL the pivots and dashboards from the namespace. But I can forget to do that) And it can take time for a large system.
What is the way to manage automatical export of DeepSee artefacts which we are editing in UI (Cubes, Pivots, Dashboards, Pivot Variables, Term lists, Shared Measures) into files every time when I push Save button?
let know the source code to fetch files from git hub repository..while running the attached file we are getting error.
ERROR #5001: Repository doesn't exist OR you don't have accesscoming1 1
We have installed IRIS on a separate server that we access remotely and copied all code and data to it so we can test IRIS before we do the move.We develop directly on the server.
Is anyone using Atelier with 3 environments (instances with multiple namespaces) (DEV, TEST, PROD) using GitHub as the source control.
I would be interested in how its all setup. So for example;
Would you have three branches for the code or 3 repo's.
Would you have three projects in Atelier to communicate with the environments and GitHub?
I have 3 existing environments that I wish to put under source control and also provide the ability to promote code between the environments in a controlled manner.
I posted a question here about a week ago about GIT. I believe we understand it well enough to use. We are still trying to determine the best flow for our needs.
But now the question is how do we integrate this with GIT?
We are new to both Git and Atelier and would love to get advice.
Currently I believe the flow would be something like this:
1.Create a branch from our origin repository (let's say Ticket 123 branch)
2.Download that branch locally to our PCs with Cache running a local instance
We are currently switching from Studio to VSCode and central GIT with Serverside Development and have a few start problems. I have set up a system with Git.
The baseline commit including remote push works.
But now I have a problem with the VSCode. When I create and compile a new class, it saves it correctly. But if I want to make further changes to the class, it saves the class and loads it again with the previous status. So the changes I made are gone again.
I installed and configure CodeTidy in my local development environment, without InterSystems source-control (git-source-control) and only git for source control.
I am new to Intersystems, in our project we are directly connecting to the server (environment) using Intersystems VSCode extensions and publishing our changes from local machine. This is not the way we usually do as development process.
Is it possible to implement continuous integration ? So that developers can check-in their code in GIT Hub and can integrate Jenkins and automate the deployment?
This article will cover turning over control of provisioning the InterSystems Kubernetes Operator, and starting your journey managing your own "Cloud" of InterSystems Solutions through Git Ops practices. This deployment pattern is also the fulfillment path for the PID^TOO||| FHIR Breathing Identity Resolution Engine.
In VS Code using the InterSystems ObjectScript extensions, I'd like the indentation applied to match that of IRIS Studio. Specifically for comments and dot syntax, I'd like pressing enter (carriage return) to preserve the current dot depth and same comment beginning.
In IRIS Studio after changing the indentation settings to custom using " \t.#/;" without quotes (note the leading space), the behaviour looks like this:
Recently GitHub introduced topics for the projects.
So you can change your InterSystems related projects introducing the topics to let it be categorized, more visible and searchable. Here is the list of good examples for your projects (some of them are clickable already):
In this series of articles, I'd like to present and discuss several possible approaches toward software development with InterSystems technologies and GitLab. I will cover such topics as:
Git 101
Git flow (development process)
GitLab installation
GitLab Workflow
Continuous Delivery
GitLab installation and configuration
GitLab CI/CD
In the first article, we covered Git basics, why a high-level understanding of Git concepts is important for modern software development, and how Git can be used to develop software.
In the second article, we covered GitLab Workflow - a complete software life cycle process and Continuous Delivery.