Any Development Teams using LANSA with VCS?

This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Post Reply
Posts: 22
Joined: Thu Oct 10, 2019 9:32 am

Any Development Teams using LANSA with VCS?

Post by LANSAfolks » Sat May 29, 2021 8:18 am

Just opening a thread for folks that are using LANSA environments with a VCS system (GIT/TFS).

Some pertinent questions.
Q1: How do you use your VCS for code comparisons and merges? Any issues/watchouts?
Q2: How do you manage development to QA source code and compiled object movements?
Q3: Work with an IBMi server in the mix?
Q4: Manage and use your Build server?
Q5: Organize and build deliveries to your targets?

More questions / discussions on the subject are welcome. Curious if folks are using such environments today and for what purpose?

Posts: 1
Joined: Fri Jun 04, 2021 4:58 pm

Re: Any Development Teams using LANSA with VCS?

Post by KEC » Fri Jun 04, 2021 5:07 pm

Yes. I've worked on a large project that is VCS with an IBMi

This is using GitHub. This becomes the master repository. The IBMi is added as a Remote server, and instead of doing a Checkin, Checkout using Host Monitor you perform a Deliver To. It is one way, as you code base is Git not the IBMi.

LANSA on the client is quite magical as switching branches quickly updates the repository to that branches state. The only issue is it can't do that for server side(IBMi). So if you have a branch with server changes(table or code) then this can become problematic. For large changes it is recommended that a separate server install is created for that branch. Even though the project I'm working on covers an entire company, I've never had a change where that has been required.

Promotion for QA / Prod is a hard one to discuss as companies work different ways. Merge to a different branch or tagging are all options. It just depends on the requirements and how you have build servers configured.

Post Reply