Le 2012-02-26 à 21:34, David Avendasora a écrit : > On Feb 26, 2012, at 10:17 AM, Pascal Robert wrote: > >> Le 2012-02-25 à 06:32, David Avendasora a écrit : >> >>> Ahg! >>> >>> I _swear_ I'm going to get this done in the next few weeks. I've been >>> working on the scripts lately to make sure they are ready. Pascal and I >>> just need to do some coordination on the all-in-one builds. And of course I >>> need to write an outline and actually do the recording / WebCast. >> >> Problems is that I don't think we can have a single script that can work >> with many situations. > > I agree. I tried to make one-script-to-rule-them-all (and-in-Ant-bind-them), > but it's just making the one script to complicated. > > I'm working on a simplified script and job description that will work for a > single wonder-based project and a slightly more complicated one that will > work for building both an Application and any frameworks it depends upon. > > (All you Maven folks, here's where you insert your smug remarks about how > with Maven all of this just works. :)
When, I'm thinking about Maven sometimes… until I have to figure out how to fix problems with it. > A lot of the assumptions made in the existing scripts don't' make much sense > in the world of Git. They worked great with SVN, but Git is just so > different, that I really need to rethink them entirely… which is part of the > reason I keep putting off the screencast. > >> For example: >> >> - WOJenkins assume that your own frameworks will be on Jenkins, with the job >> having the same name as the framework in the class path. For example, if the >> job is WO_FrameworkA and in the class path of the application, it's >> FrameworkA, it won't find it. I had this problem because I prefixed WO_ on >> all WO jobs to make sure it doesn't conflict with Xcode projects name, and I >> had to remove the WO_ prefix. > > Yes, currently that is an assumption that the current script makes, we could > add a PROJECT_PREFIX parameter so you could easily specify one, but again, > we're making the script very complicated… maybe this one would be worth it, > but… maybe there's a different way to get the same end result. But at the same time, it would fix the problem for building against two different versions of Wonder. Let's say I have two versions of Wonder, one called "stable" and the other "master". I could add the "ST_" prefix for jobs that will use the "stable" branch, and "MS_" for master. When an app is built and have a ST_ prefix, it would try to find the frameworks by looking for a job named ST_<FrameworkName>. > >> - Another example: SimpleBlog. The Git repository contains the two projects, >> and each have their own build.xml file. But since it will try to find the >> framework in another Jenkins job, you will have to have two jobs, one to >> build SimpleBlogLogic and another to build SimpleBlog, even if both are in >> the same Git repository. > > Yes, that is how the current script works, unfortunately. With SVN it wasn't > a big deal because you could checkout just one subdirectory, with Git, you > don't just checkout the source code, you're cloning the entire repository. > With some WO projects having 10 years of commits making two or three clones > of an entire repository is … wasteful. There's the concept of a shallow > clones and partial clones, but I'm not sure that the Jenkins Git Plugin > supports either of them. > >> - Same thing if you want to build projects against two different versions of >> Wonder (you might have a "stable" version of Wonder but want to build >> against master or integration to see if it works). > > Well, the current scripts support that just fine, except that you have two > clones of the Wonder repository. > > Whatever the case, the current WOJenkins scripts and job definitions are > relatively limited, but they are a great place to _start_. You will almost > certainly want to modify both in some way to make them work _exactly_ the way > you want. > > Short term advice as I work on the Screencast and All-in-one scripts: > > 1) Create your own github clone of WOJenkins > 2) Create a new branch with your changes on it > 3) Submit pull requests for new Job Definitions or workspace setup scripts > that you think will be useful to others. > > I am also planning on turning over the primary WOJenkins repository to > WOCommunity. I'll then clone it myself and work just like everyone else. > > Dave > > >> >>> Sorry to everyone that's been waiting on it! >>> >>> Dave >>> >>> On Feb 25, 2012, at 6:04 PM, Gino Pacitti wrote: >>> >>>> Hi ... >>>> Wasn't there going to be a webcast for Jenkins? >>>> >>>> Did that happen... I know the French version occurred and there were some >>>> issues came to light but were they resolved and the webcast aired. >>>> >>>> If so is there an online version. >>>> >>>> Gino >>>> _______________________________________________ >>>> 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/probert%40macti.ca >>> >>> 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]
