There will be a Copr outage starting at:
$ date --date '2020-11-13 8:30 UTC'
The outage will last approximately 3 hours. The copr-backend storage (copr build results) will be offline for a while because we need to migrate the data volume to a new machine and fix-up the networking (so things like 'dnf update' will complain for enabled copr projects). We plan to minimize the backend storage outage though (expected "full" downtime is up to 15 minutes).
Reason for outage: We're updating copr packages to the new versions which will bring new features and bugfixes. We also moving away from Fedora 31 (soon EOL) to Fedora 33.
Affected Services: copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/
Contact persons: @praiskup and @frostyx
Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.
Outage ticket: https://pagure.io/fedora-infrastructure/issue/9459
The outage is over, we'll send the release notes later today.
Thank you for patience and happy building! Copr Team
On Thursday, November 12, 2020 12:31:03 AM CET Pavel Raiskup wrote:
There will be a Copr outage starting at:
$ date --date '2020-11-13 8:30 UTC'The outage will last approximately 3 hours. The copr-backend storage (copr build results) will be offline for a while because we need to migrate the data volume to a new machine and fix-up the networking (so things like 'dnf update' will complain for enabled copr projects). We plan to minimize the backend storage outage though (expected "full" downtime is up to 15 minutes).
Reason for outage: We're updating copr packages to the new versions which will bring new features and bugfixes. We also moving away from Fedora 31 (soon EOL) to Fedora 33.
Affected Services: copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/
Contact persons: @praiskup and @frostyx
Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.
Outage ticket: https://pagure.io/fedora-infrastructure/issue/9459
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.o...
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Happy building! Copr Team
On Fri, 13 Nov 2020 at 17:26, Pavel Raiskup praiskup@redhat.com wrote:
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Many thanks for the build batches feature! I have some questions about this. Building on the example in the release notes,
- If a fourth build 101040 depends on 101020 and a fifth one 101050 depends on 101030, when do these ones start? As soon as each build, individually, finish? Or when the whole batch, 101020 and 101030, finishes?
- Then, what happens if 101030 fails?
- Can a build depend on more than one build ID?
- Are these flags (after-build, with-build) available for other build commands (e.g. buildscm)?
Thanks,
On Fri, 13 Nov 2020 at 17:50, Iñaki Ucar iucar@fedoraproject.org wrote:
On Fri, 13 Nov 2020 at 17:26, Pavel Raiskup praiskup@redhat.com wrote:
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Many thanks for the build batches feature! I have some questions about this. Building on the example in the release notes,
- If a fourth build 101040 depends on 101020 and a fifth one 101050
depends on 101030, when do these ones start? As soon as each build, individually, finish? Or when the whole batch, 101020 and 101030, finishes?
Then, what happens if 101030 fails?
Can a build depend on more than one build ID?
Are these flags (after-build, with-build) available for other build
commands (e.g. buildscm)?
build-package was a better example for this.
Thanks for questions!
On Friday, November 13, 2020 5:50:46 PM CET Iñaki Ucar wrote:
On Fri, 13 Nov 2020 at 17:26, Pavel Raiskup praiskup@redhat.com wrote:
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Many thanks for the build batches feature! I have some questions about this. Building on the example in the release notes,
- If a fourth build 101040 depends on 101020 and a fifth one 101050
depends on 101030, when do these ones start? As soon as each build, individually, finish? Or when the whole batch, 101020 and 101030, finishes?
*20 and *30 re in one batch -- so both *40 and *50 are started at the same time after the that batch finishes.
Both *40 and *50 are put into a separate batch, but that is just a detail in this case.
The currently processed batch dependency tree can be observed at: https://copr.fedorainfracloud.org/status/batches/
- Then, what happens if 101030 fails?
The batch is finished as soon as all the builds inside are finished. No matter if they failed or succeeded... so the other two batches will start building.
I know it is not ideal. In the future we could implement something more clever like "give the maintainer a chance to fix the build, before we continue...". But it would be way too complicated contribution at the start (even the actual was). Please fill the RFE if you see a space for enhancement.
- Can a build depend on more than one build ID?
You should rather think about "batches" in this case, and each batch can only depend on one batch.
Corner cases aside => --after-build-id creates a new batch, --with-build-id puts the build into an existing batch.
- Are these flags (after-build, with-build) available for other build
commands (e.g. buildscm)?
I believe they are.
Pavel
On Fri, 13 Nov 2020 at 18:13, Pavel Raiskup praiskup@redhat.com wrote:
Thanks for questions!
On Friday, November 13, 2020 5:50:46 PM CET Iñaki Ucar wrote:
On Fri, 13 Nov 2020 at 17:26, Pavel Raiskup praiskup@redhat.com wrote:
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Many thanks for the build batches feature! I have some questions about this. Building on the example in the release notes,
- If a fourth build 101040 depends on 101020 and a fifth one 101050
depends on 101030, when do these ones start? As soon as each build, individually, finish? Or when the whole batch, 101020 and 101030, finishes?
*20 and *30 re in one batch -- so both *40 and *50 are started at the same time after the that batch finishes.
Both *40 and *50 are put into a separate batch, but that is just a detail in this case.
The currently processed batch dependency tree can be observed at: https://copr.fedorainfracloud.org/status/batches/
Nice. :)
- Then, what happens if 101030 fails?
The batch is finished as soon as all the builds inside are finished. No matter if they failed or succeeded... so the other two batches will start building.
I know it is not ideal. In the future we could implement something more clever like "give the maintainer a chance to fix the build, before we continue...". But it would be way too complicated contribution at the start (even the actual was). Please fill the RFE if you see a space for enhancement.
I think a flag to automatically cancel dependent builds if something fails in a batch wouldn't be too complicated to implement. Will fill an RFE.
- Can a build depend on more than one build ID?
You should rather think about "batches" in this case, and each batch can only depend on one batch.
Corner cases aside => --after-build-id creates a new batch, --with-build-id puts the build into an existing batch.
And we can use any build ID in a batch with those flags, right? I.e., we don't need to keep track of the first one in the batch.
- Are these flags (after-build, with-build) available for other build
commands (e.g. buildscm)?
I believe they are.
Nice, thanks!
On Friday, November 13, 2020 6:44:14 PM CET Iñaki Ucar wrote:
On Fri, 13 Nov 2020 at 18:13, Pavel Raiskup praiskup@redhat.com wrote:
- Can a build depend on more than one build ID?
You should rather think about "batches" in this case, and each batch can only depend on one batch.
Corner cases aside => --after-build-id creates a new batch, --with-build-id puts the build into an existing batch.
And we can use any build ID in a batch with those flags, right? I.e., we don't need to keep track of the first one in the batch.
Correct. Pavel
On 11/13/20 5:25 PM, Pavel Raiskup wrote:
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Dist-Git packages \o/
Is there a way to edit the packages to use this via CLI?
E.g. when we added packages like this:
copr add-package-scm --clone-url https://src.fedoraproject.org/rpms/$%7Bpkg%7D.git --name $pkg --webhook-rebuild on --commit master ${copr}
How can I run copr edit-package-... or some other command to convert such packages to fedora dist-git packages?
On Friday, November 13, 2020 6:06:49 PM CET Miro Hrončok wrote:
On 11/13/20 5:25 PM, Pavel Raiskup wrote:
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Dist-Git packages \o/
Is there a way to edit the packages to use this via CLI?
E.g. when we added packages like this:
copr add-package-scm --clone-url https://src.fedoraproject.org/rpms/$%7Bpkg%7D.git --name $pkg --webhook-rebuild on --commit master ${copr}
How can I run copr edit-package-... or some other command to convert such packages to fedora dist-git packages?
The 'edit-package-*' pattern should just work: $ copr edit-package-distgit --name <package> <project> ...
Pavel
On 11/13/20 6:24 PM, Pavel Raiskup wrote:
On Friday, November 13, 2020 6:06:49 PM CET Miro Hrončok wrote:
On 11/13/20 5:25 PM, Pavel Raiskup wrote:
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Dist-Git packages \o/
Is there a way to edit the packages to use this via CLI?
E.g. when we added packages like this:
copr add-package-scm --clone-url https://src.fedoraproject.org/rpms/$%7Bpkg%7D.git --name $pkg --webhook-rebuild on --commit master ${copr}
How can I run copr edit-package-... or some other command to convert such packages to fedora dist-git packages?
The 'edit-package-*' pattern should just work: $ copr edit-package-distgit --name <package> <project> ...
Indeed, thanks. I needed:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-b9d29463b5
Does the Auto-rebuild option of such packages still include src.fp.o pull requests?
On Friday, November 13, 2020 6:30:48 PM CET Miro Hrončok wrote:
On 11/13/20 6:24 PM, Pavel Raiskup wrote:
$ copr edit-package-distgit --name <package> <project> ...
Indeed, thanks. I needed:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-b9d29463b5
Does the Auto-rebuild option of such packages still include src.fp.o pull requests?
Yes, it should.
Pavel
On 11/13/20 6:32 PM, Pavel Raiskup wrote:
On Friday, November 13, 2020 6:30:48 PM CET Miro Hrončok wrote:
On 11/13/20 6:24 PM, Pavel Raiskup wrote:
$ copr edit-package-distgit --name <package> <project> ...
Indeed, thanks. I needed:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-b9d29463b5
Does the Auto-rebuild option of such packages still include src.fp.o pull requests?
Yes, it should.
Awesome. Thanks, Pavel!
On 11/13/20 5:25 PM, Pavel Raiskup wrote:
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Happy building!
Indeed it is happy. I've just finally got to trying out the batch thing.
$ copr build-package --nowait @python/python3.10 --name python-pytest-relaxed --after-build-id 1776391 Build was added to python3.10. Created builds: 1776396 $ copr build-package --nowait @python/python3.10 --name python-invoke --after-build-id 1776396 Build was added to python3.10. Created builds: 1776397 $ copr build-package --nowait @python/python3.10 --name python-paramiko --after-build-id 1776397 Build was added to python3.10. Created builds: 1776398 $ copr build-package --nowait @python/python3.10 --name ansible --after-build-id 1776398 Build was added to python3.10. Created builds: 1776399
This is awesome!
One small suggestion: The pending builds are not visibly marked as waiting for another build (or at least I have not find the information in the web UI). That might be confusing for others when multiple people work on one copr project.
copr-devel@lists.fedorahosted.org
-
Iñaki Ucar -
Miro Hrončok -
Pavel Raiskup