Re: Source code on IFS

Re cons:
1. An equivalent to SEU at v7.3 is Notepad since you can't turn on all the syntax helpers with code written since v6.1. So, not an issue.
2. You can use Git

Re pros:
1. So open source VCS does not handle builds and deploys, but there are many CI tools that do way more than any of the IBM i change control tools I have worked with, and they are compatible with the IFS. Granted there isn't one package that does what the IBM i tools do. But, you just have to put together a set of tools like Ant for scripting the build and deploy. RPGUnit for automated testing. Granted many of the tools are still lacking IBM i support, but it is open source, and there are a lot of tools that can be ported. Linters, code sniffers, code coverage tools, all made easier buy moving to the IFS.

-----David Gibbs <david@xxxxxxxxxxxx> wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: David Gibbs <david@xxxxxxxxxxxx>
Date: 05/25/2016 03:59PM
Subject: Re: Source code on IFS


On 5/25/2016 12:53 PM, Steve Jones wrote:

Having returned from COMMON - Thank You to all the speakers that
presented, we heard some talk about having your source code stored on
the IFS.

Does anyone have some insight as to the pros/cons/why of doing this?

A few cons come to mind ...

1. You won't be able to use SEU to edit source (yes, some people still use that) or PDM to manage the source.
2. Some of the change control products won't work with source in stream files.

Pros ...
1. Open source change control products are compatible ... attractive as this may seem, keep in mind that there is a lot more to change control on IBM i than just the source code.

This maybe the wrong list to post this, so feel free to move it to
the correct list.

Absolutely correct list.

david