Source Control For Caché / Ensemble

Question

Question

Jose Sampaio · Jul 21, 2016

#Source Control #Studio #SVN #Caché #Ensemble

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.

Discussion (8)0

Log in or sign up to continue

Stella Ticker · Apr 15, 2017

At my current job, we do not have local installations of Cache. All developers work on a single windows server which serves as a development environment. There is no source/version control or central repository. I am wondering if there are source control clients that would allow several users to work off different branches but on the same machine, so that each user has their own "local" version of a repository..We want to introduce source control, branching and code reviews. However my experience with this has only been in situations where each developer has a local instance of Cache on their laptops. Any ideas on how we can solve this?

0 0

Timothy Leavitt · Jul 21, 2016

Here's the documentation on about configuring/implementing source control in Studio: http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...

0 0

John Murray · Jul 21, 2016

If you want a complete, closely integrated source control solution that's simple to add to your Caché / Ensemble environment, please take a look at our product Deltanji. This is ready for the approaching "new world" of Atelier, but equally happy working with older versions right back to 2009.1.

John Murray

Senior Product Engineer

George James Software

1 0

score 4 · Answer 1 · 2016-07-21T09:09:13-04:00

There are no particular recommended SourceControl systems. Everything depends on your choice.

Some time ago, with versions cache less then 2016.2 and before Atelier was appeared, we could use nothing except Studio. And in this case to work with particular SourceControl we should write own addon for Studio as a wrapper for this SourceControl. You can find one as a good example here on github, which works with GIT

Now, when we have Atelier, we could forget about this part, and use lots of available plugins for different SourceControl systems.

BTW, I prefer git, but most of time used SVN at work, and git for my own projects.

score 0 · Answer 2 · 2017-04-16T13:41:03-04:00

With Studio, you will have only one option, is to store sources from server's side. Any Studio plugin works in Caché, and this code could decide where to store code. But developers should also have access to the same folder. If you have authorization on your Caché server, it will be quite easy to split settings and storing sources on disk for every developer.

But If you would choose Atelier, you should not care about it. Atelier all changes store on client's side. And no matter how many developers works on one server.

score 1 · Answer 3 · 2016-07-21T17:10:29-04:00

I tried a lot of open-sourced/generally available Source Control hooks for Studio/git integration and cache-tort-git offers the best wokflow as you don't need to switch from studio window for ~95% of source control usage cases.

score 0 · Answer 4 · 2016-07-31T15:43:07-04:00

I can recommend also this very simple but robust source control tool.

It simply exports class to the certain directory after every compilation in Studio and loads it to Studio if there is updated version on disk.

It imports/exports all the classes, routines and dfi's in namespace and can do it even in UDL form.

score 0 · Answer 5 · 2017-04-17T09:13:34-04:00

I would like to emphasize that if it is a new customer or if they are considering upgrading you would evaluate the possibility of guiding your customer to use Atelier. According to the 2017.1 release notes "the focus of future development will be on the new Eclipse based IDE". See the following link for additional details:

http://docs.intersystems.com/documentation/cache/20171/pdfs/GCRN.pdf (Page 6 - 1.8 New Features in Atelier, the Eclipse-Based IDE)