[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-buildsys-list
Subject:    Re: koji chain-build usage
From:       Doug Reiland <dreiland () gmail ! com>
Date:       2010-03-04 20:50:51
Message-ID: 6844644e1003041250i2805146em70b42a1ba02fa0d7 () mail ! gmail ! com
[Download RAW message or body]

I am trying to bring another builder on line.
Would I copy the certs. from the hub over to the other system? I
generated 2 builders at that time, like the examples.
On system2, called fedora2: would I use the same koji_ca_cert.crt file

Doug

On Fri, Feb 26, 2010 at 3:28 PM, Mike Bonnet <mikeb@redhat.com> wrote:
> On 02/26/2010 03:14 PM, Doug Reiland wrote:
>> ok, I just seem to be waiting for createrepo alot.
>> Making very slow progress in package builds.
>
> Is that because you only have one builder, and its busy processing
> newRepo tasks instead of build tasks?  The simple answer is to add more
> builders.
>
> The only time you should be waiting for repo regens is if your package
> depends on a previously-built package.  In that case chain-build or
> scripting up something using wait-repo is the best option.
>
>> On Fri, Feb 26, 2010 at 2:27 PM, Mike Bonnet <mikeb@redhat.com> wrote:
>>> On 02/26/2010 02:15 PM, Doug Reiland wrote:
>>>>>
>>>>> You can emulate chain-build with a series of build and wait-repo
>>>>> commands if you like.
>>>>>
>>>>
>>>> I want to be able to improve build throughput.
>>>>
>>>> Is the following valid approach?
>>>>
>>>> koji build --skip-tag mytag srpm1 srpm2 ....
>>>> after done
>>>> koji tag-pkg mytag pkg1 pkg2 ....
>>>> koji regen-repo ...
>>>
>>> I think you're assuming that a repo-regen will block other builds from
>>> taking place.  That's not the case.  A build will use the most recently
>>> created valid repo for the tag.  Other builds can go on while a repo is
>>> being regenerated.  When the repo regen is complete, it will be marked
>>> as the new latest repo, and any builds submitted after that will use the
>>> new repo instead of the old.  Using --skip-tag doesn't improve
>>> throughput at all over using chain-build or wait-repo in between
>>> (dependent) builds.
>>> --
>>> buildsys mailing list
>>> buildsys@lists.fedoraproject.org
>>> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>>>
>> --
>> buildsys mailing list
>> buildsys@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>
> --
> buildsys mailing list
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

[prev in list] [next in list] [prev in thread] [next in thread]