> I just had a quick look - we would need to install the various java
> versions, in our (test) user - they don't provide this.
The SF people are very resonable and would most likely allow us to do this.
Also, can't we just install the JVMs in the user's home directory.
> Also, we would need to ftp the code over each night - as they are not
> linked to cvs yet either.
Last time I checked SF doesn't support ftp, but you can scp the files over.
scp is easier to script any way.
> It initially sounds good - scripts to ftp the code over, then a
> remote ssh script to build and run the tests.
Why not just send the binaries?
> The only tricky bit would be to get through the machine selection
> menu automatically in ssh - not sure how to do this.
Is is a menu shell? If so, can you change shells? Otherwise SF probally has
a work arround.
> cron and at seem to be disabled.
I think they allow some approved projects to use cron or a simmilar tool.
> The current machine options are;
>
> A. [x86] Linux 2.2 (Debian 2.2)
> C. [x86] FreeBSD (4.3-RELEASE)
> G. [Alpha] Linux 2.2 (Debian 2.2)
> I. [PPC - RS/6000] Linux 2.2 (Debian 2.2)
> L. [Sparc - Ultra60] Linux 2.2 (Debian 2.2)
> M. [Sparc - R220] Sun Solaris (8) #1
> N. [Sparc - R220] Sun Solaris (8) #2
> O. [Sparc - R220] Sun Solaris (8) #3
> P. [Sparc - R220] Sun Solaris (8) #4
We should test Linux 2.4 and Windows. Some of our users may have servers
they would be willing to let us test on. I certainlly would, if someone
could give me detailed instructions on the setup.
-dain
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
