Don't get me started on Open Access 😊
In terms of classic IBM i development, Liam's plug-in for VS Code took care of most of my issues. Works well for IFS and classic source.
Personally I am all for leaving classic source in place in source files as masters and pushing to git which gives you the best of old-style and new style classic development processes.
IFS development already falls under standard process for git, so that's not much of an issue to fit in to a CI/CD pipeline.
It will be interesting to see if more than LUG companies adopt this. Or if they even do.
Time and $$$$ will tell.
Will you be adopting Merlin ?
date: Tue, 3 May 2022 20:16:31 -0500
from: Vern Hamberg via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: Re: : IBM extends software modernization capabilities with
IBM i Modernization Engine for Lifecycle Integration (IBM i Merlin)
Your comment reminds of what you said about RPG Open Access when I suggested using it for remote database access - that we already know how to do everything without ROA. And I think I said something like, yes, but not everyone knows what you do.?? :)?? Merlin feels similar, in that it is collecting and distributing what you know to do, but the average developer will have a easier time, getting over the hurdles that you and Jack and others have figured out.
Anyhow, good memories of those good old days, eh?
On 5/3/2022 12:00 PM, Richard Schoen wrote:
I think CI/CD can be done without Red Hat and OpenShift already on IBM i using Github Actions, Ansible and other open source scripting technologies.
This is possibly a good thing, but seems to have been developed in a vacuum.
The market will ultimately decide.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.