Sounds great, thanks Jeremy. I'd heard about it, but not that it was open.

On Thu, Feb 5, 2009 at 1:13 AM, Jeremy D. Miller <[email protected]>wrote:

> Guys,
>
> For CI servers, how about just jumping onto the forthcoming
> TeamCity.CodeBetter.com?  It's meant to be open for all .Net OSS
> projects.  James Avery is helping as well. Contact him, or Brendan Tompkins
> ([email protected]) to get FNH enrolled.
>
> Jeremy D. Miller
> The Shade Tree Developer <http://codebetter.com/blogs/jeremy.miller>
> [email protected]
>
>
> ------------------------------
> *From:* James Gregory <[email protected]>
> *To:* [email protected]
> *Sent:* Wednesday, February 4, 2009 3:51:15 PM
> *Subject:* [fluent-nhib] Re: Public CI Box?
>
> There is not. I actually had the plan to have a CI server generate binaries
> for the website too, just need to find a CI server. I believe once upon a
> time James Avery contacted me about getting something setup, but nothing
> came to fruition.
>
> On Wed, Feb 4, 2009 at 3:37 PM, Steven Harman <[email protected]>wrote:
>
>> All,
>> Is there a public CI build running for Fluent NHibernate? I know
>> NHibernate proper is running over at CodeBetter, but I was just thinking
>> that it would be nice to have a public build server for FNH as well. And
>> aside from the transparency of a public CI box, I'd also like it for more
>> selfish reasons - I'd be able to pull the latest binaries right off trunk
>> (assuming the build were packaging & archiving the results).
>>
>> Thoughts?
>>
>> -steve
>>
>> //----  90% of being smart is knowing what you're dumb at  ----//
>> http://stevenharman.net/
>>
>>
>>
>
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Fluent NHibernate" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/fluent-nhibernate?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to