Hudson and frameworks reference
Hudson and frameworks reference
- Subject: Hudson and frameworks reference
- From: Pascal Robert <email@hidden>
- Date: Fri, 14 Jan 2011 10:26:09 -0500
We are moving from CVS to Git, and after that we are going to use Hudson to build the projects from Git. Now, I was wondering how WO people handle frameworks dependencies when building WO applications. So far, I see two options:
- Have jobs to build all the frameworks and put them in one location, and have wo.local.frameworks to point to that place.
- Building each frameworks "locally" (eg, in the job directory of the application that is going to be build)
Problem for option #1 is that we do have some applications that use different branches of the frameworks, so by having a central location some frameworks would be override by a install made from a different branch.
Option #2 is better, but since most applications have at least 5 frameworks, and we have over 40 applications, that means that some frameworks might be build 40 times... Not very efficient.
I guess an option would be to use a central location for stuff coming from the trunk, and that each project have a custom wobuild.properties file + a Library/Frameworks folder in the workspace of the Hudson job for the application. That "local" Library/Frameworks folder would have symlinks to the central location of frameworks coming from trunk, and if some framework is not coming from trunk, it is build with the application job.
Any opinions on that? Should I move the team to Maven just before I leave my job in one month? :-)
--
Pascal Robert
email@hidden
AIM/iChat : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti
Twitter : pascal_robert
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden