#520 Request for CI project for Kmods SIG
Closed: Fixed by pjgeorg. Opened by pjgeorg.

CentOS CI - On-boarding

Please note that Infra space is for Fedora and CentOS related projects to
consume. Decision may take some time (often up to 2 weeks) as these are decided
by the whole team.
Once decided as go, we will create you a namespace in a openshift cluster where
you can configure your CI. We do provide a Jenkins template in case you want to be
able to consume vms/baremetal nodes to perform your CI.

Please answer the following questions so that we understand your requirement.

  • How does your project relates to Fedora/CentOS?

The kmods SIG provides kmod packages for CentOS. https://wiki.centos.org/SpecialInterestGroup/Kmods

  • Describe your workflow and if you need any special permissions (other than
    admin access to namespace), please tell us and provide a reason for them.

We plan to run a scheduled task to check for new kernel releases, update package sources, and trigger package rebuilds (in CBS) as required.

  • Do you need bare-metal/vms checkout capability? (we prefer your workflow
    containerized)

No.

  • Resources required
  • PVs:

None.

Project_name: kmods
Project_admins:
 - peter.georg@physik.uni-regensburg.de

Metadata Update from @arrfab:
- Issue tagged with: centos-ci-infra, low-trouble, medium-gain

Metadata Update from @arrfab:
- Issue assigned to arrfab

acknowledge but just want to confirm that you need the jenkins setup in place (using ACO auth). I'll deploy the template as soon as I'll have (both) time and confirmation :)

Metadata Update from @arrfab:
- Issue priority set to: Waiting on Reporter (was: Needs Review)

acknowledge but just want to confirm that you need the jenkins setup in place (using ACO auth). [...]

Could you elaborate on that please? Or just let me know what I have to do ;)
I could not find any information related to this on
https://docs.fedoraproject.org/en-US/cpe/day_to_day_centos/
https://wiki.centos.org/QaWiki/CI
https://sigs.centos.org/infra/operations/ci/adding_cico_tenant/adding_cico_tenants/

when a CI project request a namespace, we deploy our template for jenkins (so it's then "dedicated" for you and not shared with other projects/tenants) and it's using ACO auth (like for everything in openshift in fact).
By default we provision the duffy api key that let you request test nodes in CI infra , so you'll have that feature even if you said "no" in your request. I'll proceed asap for this, (between other tasks)

You can connect with your ACO/FAS account on the openshift portal :
https://console-openshift-console.apps.ocp.ci.centos.org

And a jenkins pod was automatically deployed in your namespace (you'll have full admin rights):
https://jenkins-sig-kmods.apps.ocp.ci.centos.org/

Putting this ticket in feedback mode and then closing

Have done some tests. Everything seems to be working fine.

Thanks!

Metadata Update from @pjgeorg:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Log in to comment on this ticket.

Metadata