We are currently trying to migrate centos-ci used by glusto-tests from gerrit to github. Currently I have configure the webhook and have added centos-ci to the repo as admin however I see that it is still showing "Awaiting centos-ci’s response".
Can you guys please accept the collaborator request?
<img alt="Screenshot_from_2021-02-17_12-21-22.png" src="/centos-infra/issue/raw/files/652272e8b7c68a4ba334903033ef968e416577c9de6f3c4816e59db5a77c8305-Screenshot_from_2021-02-17_12-21-22.png" />
Metadata Update from @siddharthvipul1: - Issue assigned to bstinson - Issue tagged with: low-gain, low-trouble
Hello @bstinson We are currently blocked in the middle of migrating from gerrit to github on this. Any updates on this?
just for the record (had discussed with reporter in pm) I recommend 2 things instead of this 1. Using generic "adding webhook to github for jenkins" instead of adding CentOS-CI collaborator (that's all it does) and we have noticed github api limit hit multiple times (so, repeating, recommend using own account) 2. Migrating job to OCP cluster and have namespace with admin rights
Metadata Update from @siddharthvipul1: - Issue untagged with: low-trouble - Issue tagged with: medium-trouble
just for the record (had discussed with reporter in pm) I recommend 2 things instead of this 1. Using generic "adding webhook to github for jenkins" instead of adding CentOS-CI collaborator (that's all it does) and we have noticed github api limit hit multiple times (so, repeating, recommend using own account)
I do agree that this is a better way but at this point of time, I feel it would be good if we add it so that we are unblocked for the moment and later on we can work on it.
Migrating job to OCP cluster and have namespace with admin rights
I'm not sure this will unblock like you think it does. The reason we don't accept new requests is because sharing a single collaborator account exhausts a Github api limit quite quickly, so you're likely to get starved out.
If unpredictable delivery is OK with you, and if we have a better plan outlined to migrate your jobs to a dedicated instance, we can consider this.
I'm not sure this will unblock like you think it does. The reason we don't accept new requests is because sharing a single collaborator account exhausts a Github api limit quite quickly, so you're likely to get starved out. If unpredictable delivery is OK with you, and if we have a better plan outlined to migrate your jobs to a dedicated instance, we can consider this.
Thanks for the reply Brian. Currently the project is at a state where we only get a couple of pull requests in a day which is at max 5 requests on the busy days. So for now it's okay for us, if we get issues with the unpredictably we will consider modifying the CI.
Hello @bstinson Can you please accept the request and do the needful?
@kiyer have you worked with Vipul to come up with a concrete migration plan, even if that happens later?
@bstinson We only have one job so moving it doesn't really look like a huge task, we can easily do it. We have opened a ticket for the name once that's done we can migrate https://pagure.io/centos-infra/issue/248
https://pagure.io/centos-infra/issue/248 is complete and the new jenkins is up and running with access to everyone asked in ticket
closing this issue as the new namespace is up and running, please migrate the job
Metadata Update from @siddharthvipul1: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.