Infrastructure/fedora-infrastructure

Fork 0

Requesting privileges on Bodhi resources #10355

New issue

Closed

opened 2021-11-19 16:29:14 +00:00 by mattia · 13 comments

mattia commented

2021-11-19 16:29:14 +00:00

Describe what you would like us to do:

I already have access as admin to Bodhi app on OC and I would like to also ask admin permissions to:

the git repo on Github (for being able to manually merge commits when tests get stuck)
the Pypi account, for being able to update the packages there (still at 5.4)

When do you need this to be done by? (YYYY/MM/DD)

No deadline.

# Describe what you would like us to do: I already have access as admin to Bodhi app on OC and I would like to also ask admin permissions to: - the git repo on Github (for being able to manually merge commits when tests get stuck) - the Pypi account, for being able to update the packages there (still at 5.4) # When do you need this to be done by? (YYYY/MM/DD) No deadline.

mizdebsk commented

2021-11-20 00:30:10 +00:00

Metadata Update from @mizdebsk:

Issue tagged with: bodhi, permissions

**Metadata Update from @mizdebsk**: - Issue tagged with: bodhi, permissions

kevin commented

2021-11-20 19:47:23 +00:00

+1 from me here... I don't have access to the pypi account tho I don't think. I am not sure who does. ;(

ryanlerch commented

2021-11-22 05:01:01 +00:00

Owner

@abompard and @asaleh are both listed as maintainers on the main bodhi pages on pypi.

ryanlerch commented

2021-11-22 06:34:43 +00:00

Owner

@mattia i see you now in the bodhi team on fedora-infra github (i guess @kevin did that yesterday):

https://github.com/orgs/fedora-infra/teams/bodhi/members?query=role%3Amember

so that should give you commit access.

chasing up someone to get you access to the pypi packges. just so we don't miss any, these are all the bodhi packages, right?

@mattia i see you now in the bodhi team on fedora-infra github (i guess @kevin did that yesterday): https://github.com/orgs/fedora-infra/teams/bodhi/members?query=role%3Amember so that should give you commit access. chasing up someone to get you access to the pypi packges. just so we don't miss any, these are all the bodhi packages, right? * https://pypi.org/project/bodhi/ * https://pypi.org/project/bodhi-client/ * https://pypi.org/project/bodhi-server/ * https://pypi.org/project/bodhi-messages/

mattia commented

2021-11-22 07:56:05 +00:00

Author

@mattia i see you now in the bodhi team on fedora-infra github (i guess @kevin did that yesterday):

https://github.com/orgs/fedora-infra/teams/bodhi/members?query=role%3Amember

so that should give you commit access.

I've been in the bodhi group since a couple of years, I can approve PRs and manage bugs, but I've never had powers to push commits directly in any branch.
I'd like to be able to push directly to the main branch when tests are failing or we need to change required settings in the mergify file.
I think for being able to do that I need to be added in the bodhi-admin group... or a change to the bodhi group permission is needed.

chasing up someone to get you access to the pypi packges. just so we don't miss any, these are all the bodhi packages, right?

https://pypi.org/project/bodhi/

https://pypi.org/project/bodhi-client/

https://pypi.org/project/bodhi-server/

https://pypi.org/project/bodhi-messages/

Yes

> @mattia i see you now in the bodhi team on fedora-infra github (i guess @kevin did that yesterday): > > https://github.com/orgs/fedora-infra/teams/bodhi/members?query=role%3Amember > > so that should give you commit access. > I've been in the bodhi group since a couple of years, I can approve PRs and manage bugs, but I've never had powers to push commits directly in any branch. I'd like to be able to push directly to the main branch when tests are failing or we need to change required settings in the mergify file. I think for being able to do that I need to be added in the bodhi-admin group... or a change to the bodhi group permission is needed. > chasing up someone to get you access to the pypi packges. just so we don't miss any, these are all the bodhi packages, right? > > * https://pypi.org/project/bodhi/ > * https://pypi.org/project/bodhi-client/ > * https://pypi.org/project/bodhi-server/ > * https://pypi.org/project/bodhi-messages/ > Yes

asaleh commented

2021-11-22 08:47:48 +00:00

I have rights to these, just to doublecheck, @mattia - https://pypi.org/user/mattia/ is you?

mobrien commented

2021-11-22 16:16:43 +00:00

Metadata Update from @mobrien:

Issue priority set to: Waiting on Assignee (was: Needs Review)
Issue tagged with: low-gain, low-trouble

**Metadata Update from @mobrien**: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble

mattia commented

2021-11-22 17:17:39 +00:00

Author

I have rights to these, just to doublecheck, @mattia - https://pypi.org/user/mattia/ is you?

yes, it's me.

> I have rights to these, just to doublecheck, @mattia - https://pypi.org/user/mattia/ is you? yes, it's me.

asaleh commented

2021-11-23 11:49:40 +00:00

Invitiations have been sent :)

mattia commented

2021-11-23 18:09:00 +00:00

Author

Also, the Jenkins instance we're using there has a banner that says we need to migrate to the new openshift CI cluster because "it will disappear soon". We also need the migration because the old instance is using CentOS 7 (as far I understand) and there's a bug which prevents f35 or newer docker based VM to run, so tests are failing.

But I think I should open a separate issue for that?

Thank you all! The only Bodhi related thing which is left is the Jenkins instance used to perform tests upon PR submission. I don't understand if I need a CentOS account to be able to login and manage it... Also, the Jenkins instance we're using there has a banner that says we need to migrate to the new openshift CI cluster because "it will disappear soon". We also need the migration because the old instance is using CentOS 7 (as far I understand) and there's a bug which prevents f35 or newer docker based VM to run, so tests are failing. But I think I should open a separate issue for that?

asaleh commented

2021-11-29 16:31:02 +00:00

Current idea is to move to zuul, as there are few people at Red Hat dedicated to maintainig it, which could serve as a good middle ground between the barely maintained Jenkins we have and moving entirely to a hosted CI that wouldn't have budget for :)