You may not want to autocommit all code each night into SVN.
The key determining factor for me on this point is if SVN recognizes that a
commit being done is for a file that hasn't changed. My hope would be that
it would simply disregard the commit for an unchanged file. If that is true
then an autocommit each night is a solid approach to ensure code is backed
up AND all changes are logged from the last 24 hours. No coding on the i5
would need to be done on determining which source files had changed.
I wonder if maybe just using WDSC to edit members and then using Tortoise
to commit them would work.
All source members would have to make their way down to the PC. Right now
source only makes it down to the PC when you edit a specific member, and
even then it is loaded into a directory that has "temporary" written all
over it - can't rely on it IMO.
The other approach is obviously iSeries Projects, but those are simply messy
to work with (I have been using them on a project with a client as a way to
exchange source from one machine to the next and also used to change manage
it).
I think in the end it comes down to wanting EVERYTHING on the i5. That way
there is no additional setup needing to be done on each PC (i.e.
TortoiseSVN, etc) and the failure points are less. The more we keep it on
the server the less "maintenance" it needs on a per programmer basis.
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 am also very interested in this. Everytime I move forward with trying to
make it work I get caught up in something else. Is anybody using this in a
more than "playing around" capacity?
FYI: SoftLanding already tried to slip us a 12 month expiring access code
after we renewed this year :-)
Ouch. Sounds like the buyout changed A LOT of things in the company - too
bad.
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Thursday, November 29, 2007 8:46 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Automate source code backup to SVN
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
midrange.com
