Okay, this is making me _very_ sure that we should automate these:
https://pagure.io/fedora-infrastructure/issue/10441
That's because even though a human is spending time running the script, there does not seem to be any opportunity for human intervention... this happened: https://pagure.io/releng/fedora-scm-requests/issue/39869
On Wed, Jan 5, 2022 at 3:14 PM Matthew Miller mattdm@fedoraproject.org wrote:
Okay, this is making me _very_ sure that we should automate these:
https://pagure.io/fedora-infrastructure/issue/10441
That's because even though a human is spending time running the script, there does not seem to be any opportunity for human intervention... this happened: https://pagure.io/releng/fedora-scm-requests/issue/39869
We give users a web form (Pagure) that invites human input, and then an automatic-but-human-sounding-response that gives the same response over and over, or eternal silence. There's no indication in the comment that this is not a human, or a clear link to the source code to improve anything about the situation.
See my comment in https://pagure.io/releng/fedora-scm-requests/issue/19865 . I hit a despairing moment like you did. Interesting that you're able to re-open your ticket, because I don't think my account has permission to do that in this Pagure project.
Imagine if this was as easy as GitHub or GitLab, where I just click a button to create a new repo, or I run "git push" to create a new branch.
I miss the clarity and simplicity of Pkgdb.
I've mentored a new Fedora contributor through this process a while ago, and this scm-admin part was the point at which they gave up.
- Ken
On Thu, Jan 6, 2022 at 10:08 AM Ken Dreyer ktdreyer@ktdreyer.com wrote:
On Wed, Jan 5, 2022 at 3:14 PM Matthew Miller mattdm@fedoraproject.org wrote:
Okay, this is making me _very_ sure that we should automate these:
https://pagure.io/fedora-infrastructure/issue/10441
That's because even though a human is spending time running the script, there does not seem to be any opportunity for human intervention... this happened: https://pagure.io/releng/fedora-scm-requests/issue/39869
We give users a web form (Pagure) that invites human input, and then an automatic-but-human-sounding-response that gives the same response over and over, or eternal silence. There's no indication in the comment that this is not a human, or a clear link to the source code to improve anything about the situation.
See my comment in https://pagure.io/releng/fedora-scm-requests/issue/19865 . I hit a despairing moment like you did. Interesting that you're able to re-open your ticket, because I don't think my account has permission to do that in this Pagure project.
Imagine if this was as easy as GitHub or GitLab, where I just click a button to create a new repo, or I run "git push" to create a new branch.
I miss the clarity and simplicity of Pkgdb.
I've mentored a new Fedora contributor through this process a while ago, and this scm-admin part was the point at which they gave up.
I hate the scm-admin part. I hope we fix it... :(
On Wed, Jan 05, 2022 at 03:14:17PM -0500, Matthew Miller wrote:
Okay, this is making me _very_ sure that we should automate these:
https://pagure.io/fedora-infrastructure/issue/10441
That's because even though a human is spending time running the script, there does not seem to be any opportunity for human intervention... this happened: https://pagure.io/releng/fedora-scm-requests/issue/39869
Yeah. ;(
So, releng has talked about automating this for a long while. See https://pagure.io/releng/issue/9274
Long ago, a human was put in as the last line here to do quick checks of things before packages were added in case there were problems. I've not really processed them in a while (I did all of them for a few years a while back though), but I fear the volume now is so high that the human processing them (usually limb) has no time to really manually check much.
Personally, I'd like to see if we can make branch requests just use pagure-dist-git like orphaning/etc does. Just check that the user has perms to do it and that the package isn't in RHEL for EPEL requests and then just do it (or emit a message and have a toddler do it a few min later or whatever).
New packages are harder. We need someplace for someone to request the package (by rhbz #?), run all the checks we can/do already and then emit a message and have a toddler process that. I don't know if it would make sense for that to be on src.fedoraproject.org/pagure or somewhere else.
exceptions/errors could then be releng tickets (and we could try and improve the normal flow to handle them).
Anyhow, I am all for automating this...
kevin
infrastructure@lists.fedoraproject.org
-
Ken Dreyer -
Kevin Fenzi -
Matthew Miller -
Matthew Miller -
Neal Gompa