[katello-devel] Bundle install problems should be gone now

[Shannon Hughes]

other benefits include being able to share tags across RH teams. we 
could share some of the specs we are writing across departments

we could also take advantage of closure scripts to make sure runtime 
ruby deps are available before the katello rpm is built.

On 08/09/2011 09:02 AM, Lukas Zapletal wrote:
> On 08/09/2011 02:41 PM, Jeff Weiss wrote:
>> I'm curious what features Brew offers to make this pain easier?  I don't
>> know much about Brew, but apparently it runs Koji, and the Koji doc page
>> says
>> https://fedorahosted.org/koji/
>>
>> "Uses Yum and Mock open-source components"
>>
>> That's exactly what our builds (on Jenkins at least) already use.  So
>> while I am not trying to dissuade anyone from using brew, I don't see
>> how it's going to help solve this particular problem.  Maybe someone can
>> fill me in.
>
> Koji/Brew has pretty unique tagging capabilities which greatly helps 
> to resolve such errors. I am not a release engineer, but I hope by 
> defining tags, targets and buildroots we are able to prevent 
> situations when katello is built against wrong versions. Packages are 
> build directly against those from tags.
>
> I heard jblazek should become our release engineer, is this still 
> valid? What are the plans here?
>


-- 
Shannon Ray Hughes
shughes at redhat.com
Sr Software Engineer
Systems Management