I don't think Mark released a command line version of the SVN command line
program caller so you might need to see if there's a PASE version of the svn
commit code.
You might have missed this on my first post, but the SVNKit
(
http://svnkit.com) would be a perfect fit as it is 100% pure Java that can
talk to an SVN server.
So here's how I envision it working:
1) (RPG pgm) Read config file to determine what source physical file to
"sync".
2) (RPG pgm) Read each source member individually, line by line, and write
it to a same named IFS file in a temp directory. The sequence number and
date area would NOT be included in this new file.
3) (RPG and Java) Have RPG program submit to data queue the name of a file
to sync. Java on other end of data queue processes entry and uses SVNKit to
sync with server. Obviously this part would have to have an alias so the
Java would know this file should go in xyz repository in xyz folder.
4) (Java) During the commit all responses from the SVN server would be
logged in a DB2 Physical File for later review (i.e. see if there are errors
committing).
If we keep going like this we will have a pretty polished design
requirements document by EOD Friday :-)
Thoughts?
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: midrange-l-bounces+albartell=gmail.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+albartell=gmail.com@xxxxxxxxxxxx] On Behalf Of
Richard Schoen
Sent: Thursday, November 29, 2007 3:18 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Automate source code backup to 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.
SVN will only commit changed source members.
Then if you ran an auto-commit of your working source each night it
might work.
However if the source members are in source files you would have to rip
them down to PC files before committing them.
Here's a possible process flow:
- Roll thru source files and look for changes.
- Extract changed source members to selected IFS folder.
- Commit all files in IFS folder and let SVN handle the determination
and committing of just the changed source members.
I don't think Mark released a command line version of the SVN command
line program caller so you might need to see if there's a PASE version
of the svn commit code.
Just some ideas :-)
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
