Re: Hudson and frameworks reference
Re: Hudson and frameworks reference
- Subject: Re: Hudson and frameworks reference
- From: Hugi Thordarson <email@hidden>
- Date: Fri, 14 Jan 2011 21:23:03 +0000
I second Henrique's motion to try out Maven, this is what it was made for—making complex dependency management easy. Beware though; Maven comes with what you might call "a predefined mindset" and a pretty steep (albeit shorter than one thinks) learning curve. But once you learn the basics, it's pretty straightforward.
Besides… You're leaving your job in one month? Dude, it's the PERFECT time to introduce Maven!
- hugi
PS: http://www.sonatype.com/books/maven-book/
On 14.1.2011, at 20:19, Henrique Prange wrote:
> Hi Chuck and Pascal,
>
> On 14/01/2011, at 16:54, Chuck Hill wrote:
>
>>
>> On Jan 14, 2011, at 7:26 AM, 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.
>>
>> Do you always build all 40 apps at the same time?
>>
>>
>>> 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.
>>
>> That might be a reasonable option.
>>
>>
>>> Any opinions on that? Should I move the team to Maven just before I leave my job in one month? :-)
>>
>>
>> Do they owe you money? :-P
>>
>> I guess that Maven is an alternative. I am still not convinced that it will be less work or fewer headaches.
>>
>
> No matter the solution selected, some work on the infrastructure is required. That is true.
>
> In doubt, I would suggest an experiment for anyone interested in solving this kind of problem. Try to build project Wonder with Maven on your Hudson instance. After that, try to build some projects that require different versions of Wonder, e.g., WOUnit [1] or one of our experimental projects on WOBR [2] repository. The most difficult part will be to set up the environment to recognize WebObjects libraries. But you only have to do this once.
>
> [1] https://github.com/hprange/wounit
> [2] http://code.google.com/p/wobr/
>
> 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