On Mar 6, 2012, at 10:30 PM, James Cicenia wrote: > I got jenkins to build. Now what do I do?
Crack open a beer, of course! Just don't Toast Mike Schrag since he's the one that got me hooked on Hudson way back in the day at a WONOVA meeting. > Do I reconfigure Eclipse Wolips properties to point to it? No. Think of Jenkins as a totally separate thing from WOLips. WOLips is for development, Jenkins is for testing and prepping for deployment. Part of what the WOJenkins shell scripts do is manage multiple versions of WebObjects and Wonder and keep them from conflicting with each other AND other installations on the same computer. You can run both on the same computer; they work completely independently of each other. A perfect example is let's say you write code in WOLips against source code from the master branch of Wonder. With Jenkins you can have one job that builds your app against Wonder's Master branch and a second job that also builds against the Integration branch, and they can be running simultaneously without you needing to change anything. Sure, maybe you'll only actually deploy using Wonder's master branch, but wouldn't it be great to get an email from Jenkins telling you if your App doesn't work with Wonder's Integration branch within minutes of you committing your code or Wonder being modified? With Jenkins properly setup you should get the following benefits: 1) Only need Wonder (or other 3rd-party) frameworks as source code in your Eclipse workspace, no need to have them installed in /Library/Frameworks anymore 2) No longer need to remember to build and install all your frameworks prior to building your app 3) No longer need to run Ant from within Eclipse at all! 4) Easily build against different combinations of WebObjects and Wonder. 5) Immediate notification if a change in your project or any of its dependencies cause compiler errors or test failures. Dave > IF so, can someone send me a sample screen shot of theirs? > > Next. I need the latest Prototype builds for my AJAX to work on IE. > How do I configure Jenkins or whatever to test, build and deploy with that > branch? How do you include those libraries now? There's lots of ways to skin that cat, some better than others. Possibilities are: > > Thanks > James > > > > _______________________________________________ > 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/webobjects%40avendasora.com > > This email sent to [email protected]
_______________________________________________ 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]
