Hi,
On Mon, Mar 30, 2020 at 1:13 PM Miro Hrončok <mhroncok(a)redhat.com> wrote:
On 30. 03. 20 12:59, Aleksandra Fedorova wrote:
>> Put all the other feedback aside, if we actually decide that this change is
>> happening, can we not build ELN during the datacenter move [1], when Koji will
>> have a very limited capacity [2]?
> I think we should go with Kevin's suggestion and deprioritize eln
> builds from the start.
I'm afraid that this won't be good enough. Other (Fedora) builds will be
submitted with lower prio as well. For example our Python 3.N+1 rebuilds are
usually submitted as such, so the wave of 3k packages doesn't block individual
packagers. So unless Koji has multiple levels of priorities, I would have 2 choices:
- do --background and be blocked by ELN
- don't do --background and block individual packagers
I think the automatic ELN builds should be disabled during the datacenter move
(and it might be easier to actually wait for the move before the builds even
start, if that's doable on schedule).
I am not even sure that we will have the automation ready by that time.
I'd like not to wait with the change till then, because we first need
to do some preparation work, to get those infrastructure bits and
pieces - disttag, koji target, basic buildroot. Then we would do some
test runs, find issues with the process... iterate.
It will take time to even start building anything, and I'd rather not
delay this work.
But then I agree we should adjust the timeline to take datacenter move
into account.
> If this is not going to be enough for the
> datacenter move, then we can disable ELN pipelines for two weeks.
> As we will use external service (most likely Jenkins pipeline) to
> trigger the builds, we will be able to switch them on and off without
> changing anything on the infrastructure.
Thanks.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
Aleksandra Fedorova
bookwar