I have Hudson installed and it had been working. However, when I recently attempted to update a deployment, I discovered that it is not working properly anymore. Nothing has changed on the box except updates to the project source code, retrieved via SVN. Looking in the log, I get a Build Successful message followed by an IndexOutOfBoundsException from Hudson.
install: BUILD SUCCESSFULL Total Time: 4 seconds FATAL: Bounds exceeds available space : size=262144, offset=262145 java.lang.IndexOutOfBoundsException followed by a stack trace ending with hudson.model.Executor.run I realize that Jenkins is now the preferred CI tool so I am installing Jenkins on another machine as part of my debugging. Installation was successful. However, when I add a job and tell it to use SVN (SSH+SVN), it fails to authenticate. I have installed the SVN and MultiSCM plugins. We are not using SSL. Eclipse works fine on this box. I can SSH to the repository from the command line. So it has to be a problem with settings from Jenkins. This is OSX 10.6.7 and we use JavaHL for SVN. When I specify SVN+SSH, enter my user name and supply my private key (no passphrase used), the error I get is Attempting a public key authentication with username roger FAILED: svn: E210002: There was a problem while connecting to usr:22 I cannot find anything on the web for this error specifically. Nor do I know why it is trying user 22. My UID on the server is not 22. I even regenerated my keys (I used DSA) but that didn't solve the problem. On the community page, I couldn't find any info for installing Jenkins with SVN. We have not switched our repository from SVN to git yet. If anyone else is using SVN+SSH with Jenkins, I would be interested in any tips you might offer. Thanks, Roger
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
