RE: Automate source code backup to SVN

Actually, reading all these posts and suggestions on how to properly set up an environment in which RPG source is stored in a CM repository makes me wonder...

Shouldn't WDSCi simply provide this functionality out of the box, because SCM is quite an important part of any development process, especially in an RPG shop i would say because of working in a team mostly and in a business setting where it's often important to be able to record a history of changes.

Besides, as you mentioned, it's not too hard i think to add the capability in the form of a plug-in. It's just a matter of letting IBM know we need this capability in the form of a plug-in or rather, integrated into the RSE.

I think it would be better IBM provides it as standard functionality than to couble together a home-grown solution, resulting in different solutions, instead of having the "default" solution as provided by WDSCi.

WDSCi supports CVS/SVN right now through the "projects" perspective, as was mentioned earlier, because it's based on eclipse. It just happens to be that it's not integrated with the RSE. One should be able to configure a repository from within the RSE. At the moment sources are simply downloaded from the System i5 into a default windows directory. From there on the local copy is edited and when it's saved the associated sourcemember is updated. The path to this directory reflects the IFS path, like "QSYS.LIB/SOURCES.LIB/SRCFILE.FILE/PROGRAM.RPGLE". In the simplest, default case, a repository could be associated with each connection and sources are committed into the repository using the IFS path.

Jacobus

Subject: RE: Automate source code backup to SVN> Date: Thu, 29 Nov 2007 08:46:08 -0600> From: richard@xxxxxxxxxxx> To: midrange-l@xxxxxxxxxxxx> > I agree with Adam. You may not want to autocommit all code each night> into SVN. > > I'm going to ramble a bit:> > I wonder if maybe just using WDSC to edit members and then using> Tortoise to commit them would work. > > I suppose an easy push to the iSeries would then be needed to get it> into the correct source file. > > Maybe an Eclipse plugin to associate a file type to a source file for> pushing code into a source file. > > I think you can also now compile from the IFS with V5R2 and above. (Vern> told me this :-) )> > If this is the case you could just store your files in the IFS as a work> directory and commit to SVN from there even if SVN is on another server.> > I'm definitely interested in a solution, because as Aaron said Mark is> no longer with Softlanding so we're not sure how much more innovation> will go into the i5 version of SVN. Although Mark is with Collabnet so> he may stay involved with i5. > > He apparently isn't following any of the Midrange List anymore. > > FYI: SoftLanding already tried to slip us a 12 month expiring access> code after we renewed this year :-)> > Regards,> Richard Schoen> RJS Software Systems Inc. > "Get the information you need. Now!"> Email: richard@xxxxxxxxxxxxxxx> Web Site: http://www.rjssoftware.com> Tel: (952) 898-3038> Fax: (952) 898-1781> Toll Free: (888) RJSSOFT> > > -----Original Message-----> > > ------------------------------> > message: 3> date: Wed, 28 Nov 2007 11:45:50 -0500> from: Adam Glauser <adamglauser@xxxxxxxxxxxx>> subject: Re: Automate source code backup to SVN> > Aaron, I'm curious as to your current source organization, because I > think it has some bearing on how you will want to set up your SVN > sync'ing scheme for future flexibility.> > Do you have libraries something like this?> maincode - this the code to be backed up. Ideally it would always be > working code> > develab - developer library where you would make and test your changes> develag - developer library where I would make and test my changes> ...> develrp - developer library where Random Programmer would make and test> > her changes> > I think this is a common setup, and if you go the route you are planning> > (auto-commit of /maincode/ at regular intervals) you might lose some > useful SVN functionality.> > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list> To post a message email: MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/midrange-l> or email: MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/midrange-l.>