I am on a mini deadline to show progress so far. Unfortunately, ever since I got wonder source, I have been stopped at every turn pushing to the server.

So... I decided to go the Jenkins route as it seems like a good thing and with a half dozen projects now with various dependencies I thought it would be perfect.
Plus all the cool kids are using it. 

Early this morning I got the job to build and it duly put all the frameworks,both wonder and webobjects in its Jenkins directory. And this is where I lose all sense of what I am supposed to do.

I have a project that works perfectly on my dev machine via Eclipse/Wolips. This project is not under source control because my client still hasn't setup git on teamforge for me. 
I wrote them with urgency to get me git. I think this might be the problem.

Anyway, this project needs the latest Ajax/Protaculous builds for drag and drop etc. So that is my first issue. What do I do with Jenkins? I imported these frameworks from my original git pull of wonder into Eclipse.

This all works. But now what? What triggers Jenkins? How does it know anything about eclipse? Can I set up a job to not use a SCM temporarily? Of course I am learning git at the same time.

So....



I have a project PI and I am have a ERModern frameworks imported into Eclipse as I need to modify them a bit.
The three frameworks came from the original wonder git pull. Then I stupidly started messing around with the wolips.properties and PI now can't seem to see all the other frameworks. This is really where my confusion reigns. Wolips.properties is obviously still relevant. So do I point those to Jenkins?

Anyway,,, I was up till 3:00 am, got up at 6:00 and now can't think. Tomorrow is hope eternal.

Thanks for the help.

James

On Mar 6, 2012, at 9:20 PM, Paul Hoadley wrote:

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/



Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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]

Reply via email to