#6172 Grant admin permission on staging Koji to mizdebsk
Closed: Duplicate None Opened 8 years ago by mizdebsk.

Please grant me (user "mizdebsk") admin permission on staging Koji.

I am Koschei sysadmin. I need admin permission on staging Koji for purposes of testing Koschei, including:
running regen-repo tasks (kojira doesn't run regen repo when contents of external repos change)
building from uploaded srpm (without admin permission building dummy packages, which are used for testing only, would require commiting spec file to scm and I think we should avoid that)
whitelisting dummy packages (before building new packages they need to be added to tag listing)
blocking dummy packages (Koschei should auto-remove packages when blocked in Koji, I would like to test that)


Replying to [ticket:6172 mizdebsk]:

Please grant me (user "mizdebsk") admin permission on staging Koji.

I am Koschei sysadmin. I need admin permission on staging Koji for purposes of testing Koschei, including:
running regen-repo tasks (kojira doesn't run regen repo when contents of external repos change)
building from uploaded srpm (without admin permission building dummy packages, which are used for testing only, would require commiting spec file to scm and I think we should avoid that)

We have a pkgs01.stg you should be able to commit to and build from. At least we should make sure thats working (It was at one point when we were testing new pkgs).

I really don't like the idea of importing srpms. We should be able to do builds like production.

  • whitelisting dummy packages (before building new packages they need to be added to tag listing)
  • blocking dummy packages (Koschei should auto-remove packages when blocked in Koji, I would like to test that)

Sure. FWIW, I think it would be fine to make you a koji admin in stg. I'll leave the decision up to Dennis/rest of releng though.

Replying to [comment:1 kevin]:

I really don't like the idea of importing srpms. We should be able to do builds like production.
Sure, I can run builds from SCM (pkgs.stg), but I would prefer to avoid using names conflicting with real Fedora packages so I'll at least need some package names added to tag listing, for example koschei-test-pkg1 through 100:
{{{
stgkoji add-pkg --owner mizdebsk f23 $(for i in $(seq 100); do echo koschei-test-pkg$i; done)
}}}

Replying to [comment:2 mizdebsk]:

Replying to [comment:1 kevin]:

I really don't like the idea of importing srpms. We should be able to do builds like production.
Sure, I can run builds from SCM (pkgs.stg), but I would prefer to avoid using names conflicting with real Fedora packages so I'll at least need some package names added to tag listing, for example koschei-test-pkg1 through 100:
{{{
stgkoji add-pkg --owner mizdebsk f23 $(for i in $(seq 100); do echo koschei-test-pkg$i; done)
}}}

That should all be done from staging pkgdb. testing the full process for adding new packages. I guess by whitelisting in the initial request you mean adding the package to koji. I do not see that you need admin perms for any of that. it is things that should all happen as part of the normal workflows. add or retire a package in staging pkgdb should add and block in koji. any time a package is added or blocked koji will generate new repos. or if you do builds. I do not see a need to grant permission just to make newRepos and builds should all be from staging pkgs. there are times in production that a newRepo needs generated for epel, without giving admin permissions, I would be okay with working out a way to enable people to request a newrepo for a limited set of targets, developing it in stage makes sense.

Replying to [comment:3 ausil]:

That should all be done from staging pkgdb.

Then can you point me to documentation how to request new package in staging pkgdb, or in case such documentation is missing, explain it yourself?

Replying to [comment:4 mizdebsk]:

Replying to [comment:3 ausil]:

That should all be done from staging pkgdb.

Then can you point me to documentation how to request new package in staging pkgdb, or in case such documentation is missing, explain it yourself?

Well, it works just like the production pkgdb: go to: https://admin.stg.fedoraproject.org/pkgdb/ click on the big blue button: Request new package that should bring you to https://admin.stg.fedoraproject.org/pkgdb/request/package/ and enter the information :)

You can then see/check the request under the My Requests tab in the menu

Replying to [comment:5 pingou]:

Replying to [comment:4 mizdebsk]:

Replying to [comment:3 ausil]:

That should all be done from staging pkgdb.

Then can you point me to documentation how to request new package in staging pkgdb, or in case such documentation is missing, explain it yourself?

Well, it works just like the production pkgdb: go to: https://admin.stg.fedoraproject.org/pkgdb/ click on the big blue button: Request new package that should bring you to https://admin.stg.fedoraproject.org/pkgdb/request/package/ and enter the information :)

I've already done that, but there was no response in 12 days (request ID 11, status "pending").

https://apps.stg.fedoraproject.org/datagrepper/id?id=2015-d1dd5184-c99f-4dfb-ac1b-1a107bc852bf

That's because there are no rel-eng people monitoring pkgdb in stg, should the package be added to pkgdb?
Do you need this one in particular?

Added proposed patch for ansible

We should approve mizdebsk's request to be a staging koji admin so that he can get his work done.

We can't ask him to file requests into a staging pkgdb queue that no one is watching.

We don't need another queue to monitor (certainly not in staging where we'll block development work).

Metadata Update from @mizdebsk:
- Issue set to the milestone: Fedora 22 Final

7 years ago

Login to comment on this ticket.

Metadata