Re: Automate source code backup to SVN

Hello Aaron,
I will try to explain it in a little more detail.

From my experience coding directly in the AS400 (SEU) was a wrong approach

(the speed in typing was very much slower). So I have moved all the sources
to PC and coded directly there (you can use Notepad or any editor.. I just
chose gVIM because of excelent scripting capabilities).
I coded on the PC and then run a simple command (combination of keys in
gVim) to put the source on the AS400 - with FTP. Then I would copile it
directly on the AS400, see the errors and go back to my editor and fix them.
This has improved the speed in writing code amazingly.

The next point was to install SVN on a Windows server (you can do it also on
your own computer) and use it with all my team. Everybody was using the same
scripts and everything, we had backups of the SVN on windows, Tortoise
working great, everybody happy.

How we are coding at this moment? In the library list, the programmer
library is on top of the dev library. The "FTP put" uploaded the sources on
the programmer library, so that the programs will not get screwed in all the
company in case you are modifying one important module. When the initial
testing is finished and you are doing a commit (on the PC) a simple script
runs that puts the modified files into the dev library and also compiles
them (if you have commited than it means that they will compile with no
errors).

In this case you will commit only the modified files and do not recompile
everything during the night...

Google code uses also SVN and you can host your projects at their machines
so you can grant commit rights to almost everyone you want and use also
Tortoise, etc... It's the server not being in your own company but at
google. Except that, everything stays the same. So that means, everybody
happy. And as a plus, you can do a checkout from home :))

Thanks
mihai

http://rpgcrud.ro
tzighi@xxxxxxxxx





On 11/29/07, Aaron Bartell <albartell@xxxxxxxxx> wrote:

Very interesting approach. Is the process fast for interative
development?
(i.e. edit, then save, then compile, then run, then start over)

How are you using Google code in relation to your RPG? Do they have SVN
servers you can commit to for open source projects?

Thanks Mihai,
Aaron Bartell

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mihai CARSTOIU
Sent: Thursday, November 29, 2007 4:20 AM
To: Midrange Systems Technical Discussion
Subject: Re: Automate source code backup to SVN

Hello,
How I am doing things now:
I have SVN installed on windows and TortoiseSVN for all developers. We are
developing our programs in gVIM as it is a far better editor than SEU
(hell
even Notepad is :) ). Than we use (from gVIM but can also from command
line)
a simple command to put the sources on the iSeries using FTP in our own
library. When we are happy with the source we commit it in Windows. At
commit we have an automated process that copies the sources into the main
developers library (under user's library in user list) and compiles it
depending on the extension (RPGLE, PF, DSPF, etc).

So the process is quite automated and we are very happy with it - it works
a
lot faster, you can store your sources everywhere and you can even use
google code (http://code.google.com) with it


Best regards,
Mihai

http://rpgCRUD.ro
<http://rpgcrud.ro>tzighi@xxxxxxxxx



On 11/29/07, Adam Glauser <adamglauser@xxxxxxxxxxxx> wrote:

Aaron Bartell wrote:

I would only have three libraries [...] PROD, TEST, DEV.

A developer would make all their changes in the DEV library (not their

own

library). Each time they saved the member a SVN comitt would happen.
When they were done with their coding they would move the member to

TEST

at which point another trigger would happen that would submit that

source

to another
SVN folder. The same would happen when promoting to PROD.

Well, that seems like a pretty reasonable way to get started. It buys

you

the version history functionality that seems to be your main goal. I'd
suggest that committing every single save to the DEV library might be a
bit
excessive, but that just me. I haven't used SVN enough yet to know
whether
a really large number of commits could get unwieldy in practice.

The nice thing about your approach is that if you want to get some of

the

other benefits of using SVN (like branching and tagging), it should be
fairly easy to modify or augment the process. For example, as your team
gets more comfortable with SVN, you might each want your own working
directories instead of a single working directory. This would allow two
people to collaborate on the same parts of the code at the same time

more

easily, or try out different directions of development simultaneously.

Hope this is of some use,
Adam
--
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.

--
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.

--
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.