Hi James, On 07/03/2012, at 6:55 AM, James Cicenia wrote:
> I am tired, confused, and i need to figure out how to get my code working > properly on the test server. Firstly, are you on a deadline? Or just sick of it all? Jenkins can be a bit of a time sink—every time you make a significant change, you sit through a new build, and the hours can rack up. Have a rest. Come back tomorrow. > I am sure one of you deployment/Jenkins gurus could probably figure this out > in 15 mins. I have > spent 16 hours and am more confused then ever. Can you walk us through the specific problem? This is you from another thread: > Do I reconfigure Eclipse Wolips properties to point to it? > IF so, can someone send me a sample screen shot of theirs? It's not at all clear to me what you mean here. The build server (even if it's on the same machine on which you're doing development) should pretty much stand alone from anything else you're doing. Some kind of commit trigger or polling should be triggering a new build on Jenkins, which should be pulling your project(s) from source control. Development and building should be at arm's length. How did you envisage getting WOLips involved with Jenkins? Re-quoting from above: > i need to figure out how to get my code working properly on the test server. Jenkins just builds your projects, and puts the artefacts somewhere. So on the simplest level, the answer here is: go grab your build artefacts, transport them to your test server, and deploy them in whatever is the conventional way for you. There's no magic here, you just grab Foo-Application.tar.gz and Foo-WebServerResources.tar.gz and do whatever you'd normally do with them. -- Paul. http://logicsquad.net/ _______________________________________________ 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]
