Git

Syndicate content 8 

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 previous 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. Still, our focus was on the implementation part of software development, but this part presents:

  • GitLab Workflow - a complete software life cycle process - from idea to user feedback
  • Continuous Delivery - software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software faster and more frequently.

Last comment 1 March 2019
+ 5   0 4
1001

views

+ 5

rating

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

Last comment 26 February 2019
+ 2   0 3
610

views

+ 2

rating

Hi,

I'm in the process of trying to convert my team to a Git-based workflow for source code version management (we use Ensemble and HealthShare, but build a lot of customizations on top). We are having a hard time working with Atelier in this regard for a few reasons

Last answer 3 May 2016 Last comment 29 January 2019
+ 2   0 1
965

views

+ 2

rating

Everybody has a testing environment.

Some people are lucky enough to have a totally separate environment to run production in.

-- Unknown

.

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
  • GitLab CI/CD
  • CI/CD with containers

This first part deals with the cornerstone of modern software development - Git version control system and various Git flows.

Last comment 22 November 2018
+ 9   1 5
1476

views

+ 9

rating

Hi,

We have a few projects and some of these projects share code "libraries". Some of which are persistent classes that are used by multiple systems. All these are currently deployed on Ensemble. We want to move some of the smaller ones to the cloud and make use of IRIS.

The challenge is that once we synchronise the code to IRIS from Atelier, then IRIS changes the storage definitions, which then creates changes to the files. We do not want to commit all these changes to git as it will happen again once someone synchronises with Ensemble. The developers also need to be able to make changes to the classes, regardless of whether it is deployed to Ensemble or IRIS.

Ensemble: <Type>%Library.CacheStorage</Type>

IRIS:  <Type>%Storage.Persistent</Type>

Last answer 20 October 2018 Last comment 20 October 2018
+ 2   0 1
105

views

+ 2

rating

Hi

I'm starting work with the Atelier. 

Starting from the point that Eclipse uses local files on the workstation, COS development can be versioned with market tools (For example GIT or Subversion).

I would like to know how the community has worked with code versioning, to create a consistent versioning model.

I initially have the following doubts:

  1.  Creation of WorkSpaces and Projects
  2.  Merge files
  3. Change Branch Functional Development
  4. Promotion of Environments: Development -> Homologation -> Production
  5. Generating Historical Tags

Thank you all.

This post has been translated by Google Translate, sorry for writing errors

Last answer 13 September 2018
+ 5   0 2
0

comments

182

views

+ 5

rating

Hi, Community!

Continuous Delivery is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software faster and more frequently. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production.

Join us at 07:00 UTC, April 24th for a webinar with a live demo "Git flows and Continuous Delivery" by @Eduard Lebedyuk 

The language of the webinar is Russian.

Also, see the related articles on DC.

Last comment 9 August 2018
0   0 2
175

views

0

rating

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
  • Why containers?
  • Containers infrastructure
  • CD using containers

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.

In the third article, we covered GitLab installation and configuration and connecting your environments to GitLab

In the fourth article, we wrote a CD configuration.

In the fifth article, we talked about containers and how (and why) they can be used.

In the sixth article let's discuss main components you'll need to run a continuous delivery pipeline with containers and how they all work together.

In this article, we'll build Continuous Delivery configuration discussed in the previous articles.

Last comment 4 July 2018
+ 6   2 7
576

views

+ 6

rating

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

3. Checkout Ticket 123 branch locally

4. Create a project in Atelier (let's say Ticket 123 project) and point it to a working folder (not the Ticket 123 git branch)

5. Import the files that you need from Ticket 123 git branch into your Ticket 123 project

6. Make your modifications

7. Copy those modified files from the working folder into the Ticket 123 branch folder

8. Push the local branch into  the origin branch

Last answer 31 May 2018 Last comment 31 May 2018
0   0 4
251

views

0

rating

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

+ 7   2 4
0

comments

626

views

+ 7

rating

We are going to start using Git within Cache.

One question came up - if the branch that you checked out does not have the class or mac file, what is the correct thing to do?

Should we delete from Cache or should we just keep it?

I'm leaning more towards deleting it because Cache should reflect what is in your work folder in git. But other team members are saying to keep it.

Last answer 20 April 2018 Last comment 20 April 2018
0   0 4
200

views

0

rating

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

Last answer 7 April 2018 Last comment 7 April 2018
0   0 2
127

views

0

rating

One of the benefits of Atelier is easy integration with source code management tools. Some Eclipse installations include the EGit plugin, or you can install it from the Eclipse marketplace. EGIt makes integration with Git and GitHub easy. Here are the steps I used to connect Atelier to a GitHub repository:

Last comment 23 March 2018
+ 8   0 4
1496

views

+ 8

rating

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.

I this article we'll discuss:

  • GitLab installation and configuration
  • Connecting your environments to GitLab
+ 1   0 1
0

comments

499

views

+ 1

rating

Hi, Community!

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?

Last answer 7 March 2018 Last comment 7 March 2018
0   0 2
133

views

0

rating

Hi

I am in the process of trying to implement version control software with studio.  Has anyone got any recommendations (either Linux based/windows based) as a place to start I have installed Gitlab and I wanted to know whether anyone has come across any obstacles using this.

I was also wondering whether anyone has developed any hooks for Gitlab that works well with Studio as I would prefer if there was a more integrated solution with studio?  Any help with this would be great.

Thank you.

 

Kind Regards,

 

Salma

Last answer 19 January 2018 Last comment 22 January 2018
0   0 4
380

views

0

rating

Hi, Community! 

This week we have two videos. Check the second Developer Community Video of the week:

Atelier: May the Source Be With You

 

0   0 1
0

comments

157

views

0

rating

Hi, Community! 

This week we have two videos. Check all new  session recordings from Global Summit 2017:

1. Atelier and Automated Private Instances

 

0   0 1
0

comments

166

views

0

rating

Hi

When trying to sync a class to the server where the server class has been updated by another user, I, as expected, get the Conflict Resolution Wizard.

I can then use the wizard to copy code from the server side to my local copy using the arrows also as expected.

But when I have integrated the remote code into what I think is my local copy how do I save it so that it gets integrated into my local copy and synchronised to the server.

I find if I click the 'Save Local Copy' button it ignores the changes I have made in the wizard and simply overwrites the remote class with whatever I had originally in my local copy

Last answer 22 September 2017 Last comment 19 September 2017
0   0 5
308

views

0

rating

Is your development team following best practice now that source control and continuous integration testing are better supported by InterSystems new IDE Atelier?

Many teams are turning to Git as their version control system of choice because it never locks files, among other reasons.  These teams may also be following a multi-server development workflow where changes are migrated from a DEV server to a TEST server to a PROD server. How should these teams organize their repository given this configuration?

Michelle, Atelier Technical Lead, will walk us through the below 3 tasks with an example Git repository. She will also share with us some of her favorite tools.

+ 4   0 3
0

comments

567

views

+ 4

rating

I want to demonstrate using Git via Server-side Source Control hooks (to allow both Studio and Atelier to access a Shared Dev namespace), and I was planning to use the popular Caché Git hooks:

https://github.com/intersystems/cache-tort-git 

Unfortunately, when I installed and configured them I realized that they will not work in a Shared Dev configuration because those hooks rely on calling the TortoiseGit Windows executable, which means that your IDE and your Caché instance must both be running on the same machine (this doesn't make sense for Shared Dev configurations).

Can anyone point me to examples of Git hooks for Studio which do not rely on calling a UI executable, but rather rely on the CLI for Git so they can run on a different machine than the IDE?

Thanks in advance for any suggestions you can offer.

Ben

Last answer 2 September 2017 Last comment 30 August 2017
0   0 2
325

views

0

rating

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 was thinking there might be a way to get that Info because of the fact of being logged in through Studio somehow it would help register that. 

Last answer 20 August 2017 Last comment 21 August 2017
0   0 1
214

views

0

rating