On 19/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
You have to run the outter build first and what we want ultimately is
use a test remote repository before the ITs run. We have a problem
with them being coupled to the real central. The ITs should
ultimately be completely self contained. So that's what I'm moving
toward so there are for certain some inconsistencies while I move
that way.
Anything you see like that the plan is to start from nothing,
populate the test remote repository with the IT plugins and artifacts
and then run the ITs. The old versions of the ITs artifacts were
deployed to central and the new ones I did not so you're going to
find some glitches. The overriding concern is the make it self
contained. To use a file based remote repository first, then the next
stage would be to use the ITs with a test web-based repository, then
FTP ... you see where I'm going. Get the base ITs going and then test
all our transports, test all our SCM providers ... Take a look at the
notes in the IT directory. We have production plugins coupled with
many ITs and in each of those listed cases test plugins should be
made. Specific tests of a give plugin should be ITs in that
particular plugin.
I'm sure you're going to find some problems but that's the general
plan. So even if you sketch out a bash/ruby script to setup the test
repo before running that's the kind of work we need to get done.
Okay, I can see the direction you're heading towards with making the
ITs self-contained, I just wanted to make sure it wasn't failing due
to my local set up. I can live with a failing it0002 for now.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
