On Oct 3, 2012, at 2:57 PM, Pascal Robert wrote: > > Le 2012-10-02 à 18:02, Roger Perryman <ro...@xeotech.com> a écrit : > >> The following is just an update in case anyone stumbles upon this same >> problem. Not really a full solution but perhaps useful none the less. >> >> I was not able to get SVN+SSH in Jenkins to work on an OSX 10.6.7 system >> that otherwise can access the repository via command line and Eclipse. If I >> manually import the project it works fine but the defeats the purpose. >> >> I decided to upgrade Hudson to Jenkins on the original build server (OSX >> 10.5.8) that was throwing IndexOutOfBoundsExceptions, even though the actual >> compile was successful. I shut down Hudson (it was manually launched) and >> then installed Jenkins using the OSX package (as I did on the 10.6.7 >> system). I then created a test job and it worked fine. Then I created a >> simple test project and manually copied it into Jenkins. It worked fine. >> Next I added a project that was in SVN and configured it to use svn+ssh, >> entering my user name and supplying the private key (id_dsa). It worked the >> first time. I then entered the remaining jobs from the Hudson install into >> Jenkins. >> >> Everything _appeared_ to work. >> >> However, I am noticing that one of the projects fails to build because it >> cannot find some symbols from an included framework. These changes are new >> but they do show up in the Jenkins workspace for that framework. What I >> noticed is that the build.xml file in the referenced framework is different >> in the Jenkins version than it is in the Eclipse version. All the other >> projects have identical build.xml files. I've removed all of the build >> output but it doesn't seem to make a difference. Not sure where else to >> check. >> >> Another problem that I am having (on a separate project that does build >> successfully) is "Archiving the artifacts." I've set up the post-build >> action using the config files from Hudson version (where it worked). It >> complains that the dist folder doesn't exist. Creating it did not solve the >> problem. There must be a part that I am missing that compresses the build >> output and copies it to the dist folder. In the files to archive field, I >> have "XeoMed/dist/*.tar.gz". I want to get this step working before >> exploring the "Publish over SSH" plugin to automate pushing the build >> tarballs over to the deployment server. I will still manually install them >> but it should be a matter of just expanding a few files. Does anyone have a >> working example for this scenario? > > I don't have an answer for your problem, but for the Publish over SSH part, > you can have a look at my wodeploy.pl script that will ship the archive of > the app (and the archive of web server resources), decompress it, moving it > to the correct location and restarting the app (or adding it to Monitor if > the application don't exist).
Where would I find the wodeploy.pl script? And what about instruction for installing and using it? >> Thanks. >> >> On Sep 28, 2012, at 5:27 PM, Maik Musall wrote: >> >>> >>> Am 28.09.2012 um 22:36 schrieb Roger Perryman <ro...@xeotech.com>: >>> >>>>> But the auth method would more likely involve not supplying your private >>>>> key somewhere, but add the public key of the user jenkins is running >>>>> under to the authorized_keys on the svn server. Did you do that? >>>> >>>> I submitted before fully answering the question. I generated a key (DSA) >>>> and placed the public key in authorized_keys2 on the server. This works AS >>>> ME. I supplied the private key to Jenkins so that it could establish a >>>> handshake with the server. I may need to add a Jenkins user on the SVN >>>> server otherwise, if I get this to work, I would get all the credit (or >>>> blame) for any activity from the build server. >>> >>> I think I have to let someone answer that who has experience specifically >>> with svn+ssh on Jenkins... >>> >>> Maik >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca >> >> This email sent to prob...@macti.ca > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
