First, thanks everyone for the cogent responses. After a big salad and
some chicken enchilada soup, I'm now energized to tackle this problem
with renewed vigor... :)
On May 12, 2009, at 11:40 AM, Mike Ralphson wrote:
I'm not familiar with the AS400 or SEU but do developers currently
have a complete copy of the tree to themselves, or do they only check
out the files they're editing?
They only check out the specific files they need, unfortunately.
I'm not sure what Rational Developer is likely to want to do in terms
of getting the edited files back to the AS400 (assuming it supports
that directly). Are you planning to run (j)git on the AS400 or have
another step to get the code from a central git repo back to the
AS400(s)?
Since I work with, but am not a part of, the AS400 group, I don't have
a copy of Rational to play with. I have used Websphere Studio before,
though (which I think is the precursor to Rational/eclipse) and it
used the toolbox utilities (JT400 et al) to transfer files locally,
allow the developer to work on the file, then put them back on the
server where they can be compiled. I would assume Rational works
similarly. This is making me wonder whether any open source scm will
work for this scenario. We may be tied to IBM's tools or nothing.
Is any deployment done to a test server? Is there a release process
you need to integrate with?
We have a test/release cycle that the AS400 group calls
"implementation" that is basically copying stuff from a development
400 to the production 400. I'm not sure what role an alternative scm
would play in this scenario. There's also a fantastically cumbersome
reverse implementation process called a "refresh", which copies data
files from production back to development and basically clobbers
whatever is on development. Only developer libraries are left
untouched. This seems to me to be a process which could, shall we say,
use some improvement. :)
Our devs expect their changes to go live at midnight after they
'release' them. Are there similar assumptions for you?
Our deployments have to go through some SOX-compliance ring-around-the-
rosie, so they don't really have any assumptions as to when changes
are pushed to production. I could see hook scripts filling doing some
of the work here. But some manual intervention will be required for
compliance reasons.
Thanks!
Jon Brisbin
Portal Webmaster
NPC International, Inc.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html