In software engineering, continuous integration (CI) is the practice of merging all developer working copies to a shared mainline several times a day.
Which is tool/script use of Automating the Ensemble part? Is seleinium can be used. Please help me out on Automation testing
I'm moving *D globals from DatabaseA to DatabalseB.
After importing globals I need to rebuild indices for all the imported persistent classes.
Colleagues, maybe you know one command which does it for all the classes in Namespace?
Hi, Community!
Is there an option to get an archived file of globals in one command. Say for:
Do $System.OBJ.Export("Class1*D.GBL,Class2*D.GBL","data_gbl.xml")
get something like:
Do $System.OBJ.Export("Data*D.GBL","data_gbl.gz","gzip")
And also to have the convenient one click way to import it to the namespace via terminal or Control Panel?
If anyone already has this module, share please?
It would be very convenient for import/export/continuous integration purposes cause globals can be really heavy.
Recently I started working with GitLab - GitHub self-hosted foss alternative. So far so good, liked the UI, ease of administration, and available functionality (I was on Phabricator previously, and still use it for repo mirroring).
GitLab has GitLab CI (GitLab Continuous Integration) which looks promising (pluggable docker/vm/ds to run code) , but I wondered if someone uses it already and can share scripts for it?
Just curious how many companies use in their work Docker containers, I mean not only with InterSystems products. And if such companies exist, which of them uses docker and doesn't use it for InterSystems products by some reasons. What are the reasons? For companies which already uses InterSystems in containers, how do you use it? Development environment, testing or even in production ?
And if you don't use but thought about it, what are the reasons which stop you.
As for me, I've been using InterSystems Caché inside a Docker container in some different cases:
Hi All
I have a question on working with dev and prod environments.
After project is ready and signed, I usually migrate outcome to production using the export tool from the studio.
For changes/adding to existing projects, I exclude the production class (as it has some different values differing the dev from the live) and I add the differences manually afterwards.
My questions on migrating are:
Does anyone has (to share) his/her best practice steps on "migrating dev to prod"?
Does the export action (in management portal) is better to use?
Thanks
Gadi
Hi!
I am about to configure a server with continuous integration for a client. I found that our Russian friends have again come up to the rescue and developed not one, but two continuous integration tools for Git and Caché:
My question is simple: What are the most important differences between the two and which one is going forward so I can choose the right one?
Kind regards,
Amir Samary
Hello everyone,
Does anyone know how to create integration tests using the Cache unit test framework in order to test an Ensemble production?
For example, what would be the best way to create automated tests for a BPL that calls multiple business operations (SQL, WebService ...)?
Should we create some kind of mock service/operation to simulate the response from the business operations ?