So @ryanlerch created a side-tag in staging koji earlier today and it took 45minutes: https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90060483
Do we have any way to run a createrepo task for non side-tag to see how long/quick side-tags are compared to non side-tags ?
The idea is to try to guess from this how quick things will be in prod (assuming staging is slower than prod).
@mikem If you want to subscribe to this ticket to get the following notifications :)
I've requested generation of build repo for non-side tag f30-build: https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90061742
@mizdebsk this is for an existing repo though right? So it updates an repo not creating one from scrach?
Right. For totally new repo you can see eg. this task: https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90000000
@mikem so https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90000000 ran in 38 minutes, while the side-tag https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90060483 ran in 45 minutes
Do you want me to open a koji ticket to track this? Or do you see something we did wrong?
So I've just tried to create a f30 side-tag in prod:
$ fedpkg request-side-tag --base-tag f30-build
Side tag 'f30-build-side-13911' (id 13911) created.
Use 'fedpkg build --target=f30-build-side-13911' to use it.
Use 'koji wait-repo f30-build-side-13911' to wait for the build repo to be generated.
$ time koji wait-repo f30-build-side-13911
Successfully waited 0:44 for a new f30-build-side-13911 repo
koji wait-repo f30-build-side-13911 0.34s user 0.05s system 0% cpu 44.951 total
And a f31 side-tag in prod:
$ fedpkg request-side-tag --base-tag f31-build
tie kSide tag 'f31-build-side-13913' (id 13913) created.
Use 'fedpkg build --target=f31-build-side-13913' to use it.
Use 'koji wait-repo f31-build-side-13913' to wait for the build repo to be generated.
$ time koji wait-repo f31-build-side-13913
Successfully waited 0:44 for a new f31-build-side-13913 repo
koji wait-repo f31-build-side-13913 0.32s user 0.04s system 0% cpu 44.906 total
I'd say this is looking good! :)
I think this ticket can be closed now, we'll re-open if we need to but so far it seems to be working as we want it :)
Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
to comment on this ticket.