Re: Hudson and frameworks reference
Re: Hudson and frameworks reference
- Subject: Re: Hudson and frameworks reference
- From: David Avendasora <email@hidden>
- Date: Fri, 14 Jan 2011 12:34:12 -0500
Hudson? What's Hudson?
Don't you mean Jenkins?
http://www.hudson-labs.org/content/hudsons-future
Dave
On Jan 14, 2011, at 12:24 PM, Henrique Prange wrote:
> Hi Pascal,
>
> On 14/01/2011, at 13:26, Pascal Robert wrote:
>
>> 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.
>>
>
> Option #3: Use a Repository Manager and a tool that handles dependency management for you.
>
> PRO: It solves the above problems in a way widely used/supported by the Java community.
>
>> 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? :-)
>>
>
> That seems like the best option IMHO. :)
>
> Maven integrates very well with Hudson. In most cases, you just have to configure the source URL and the goals you want to execute. Maven does all the job for you, including dependency management.
>
> Cheers,
>
> Henrique _______________________________________________
> 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
>
>
_______________________________________________
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