It seems I can't assign myself to the issue.

@ngompa Could you give me the permissions?

Done!

I created a request for new namespace in OCP4 for pagure
https://pagure.io/centos-infra/issue/665

It looks like we already have a namespace in OCP4, it just isn't set up.

I took a look at this today, but I would like to have admin access to pagure project itself, so I can setup the CI related settings. In the meantime I'm fixing the issues in the new OpenShift Jenkins instance. See https://pagure.io/pagure/pull-request/5310

@ngompa @pingou Could I get the admin permissions?

The tests are now being executed on the new Jenkins instance, but the notification about result is failing.

For Pull Requests to work we need to change the webhook for Pagure CI to https://jenkins-pagure.apps.ocp.ci.centos.org/job/pull-requests/build?token=TOKEN_NAME
TOKEN_NAME is still the same, just the url is changed

@ngompa @pingou Could you change this, or give me rights, so I can do it by myself?

I updated the URL for Pagure CI to point to https://jenkins-pagure.apps.ocp.ci.centos.org.

I'm not able to login to that Jenkins instance, though. It redirects me to id.centos.org and says that I don't have the authorization to log in.

huh, now I can log in. So anyway, I updated the thing...

@zlopez, you now have admin permissions.

@ngompa Thanks

I was able to manually trigger the job for test PR, but it seems there are some issues with pagure-ci. Where the sources for pagure-ci are located?

https://pagure.io/pagure/blob/master/f/pagure/api/ci/jenkins.py

https://pagure.io/pagure/blob/master/f/pagure/lib/lib_ci.py

The migrations it's finished. The tests are being triggered, users can see the job result and the notification from the job is sent correctly.