#8776 [jenkins] project request: oddjob
Closed: Fixed 3 years ago by siddharthvipul1. Opened 4 years ago by abbra.

I'd like to add Jenkins integration into oddjob upstream project

  • project name: oddjob
  • description: oddjob is a daemon that allows to reliably perform actions on behalf of non-privileged requesters in secure way. Primary uses are creating home directories from PAM and integration within FreeIPA for inter-master communication.
  • contact person/admin: abbra
  • url of the project: https://pagure.io/oddjob

I am preparing an upstream CI testing for oddjob to be able to validate complex interactions with FreeIPA.


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

4 years ago

@smooge @abbra

I have a question
Does this project need to a separate namespace (separate jenkins master) or would this fit in fedora-app namespace [0] or fedora-infra [1] or something else.

If it's the latter, anyone from sysadmin-jenkins group (or direct admin could create a project for them and give them the access)
I could also do it but I would need a +1 from admins from the namespace admins.
If this requires a separate namespace (less preferred), this will have to wait on bstinson who is less likely to have even an hour of free time from all the things on his plate (afaik)

[0] https://jenkins-fedora-apps.apps.ci.centos.org/
[1] https://jenkins-fedora-infra.apps.ci.centos.org/

I don't know, you tell me.

I have three upstream projects, all hosted on Pagure, to which I want to add CI. These are 'slapi-nis', 'bind-dyndb-ldap', and 'oddjob'. They are not really related to Fedora apps and Fedora infra, they are just upstream projects heavily used in FreeIPA deployments.

These Jenkins projects will be used to have pipelines that drive CI tasks for all of these projects on Azure Pipelines because both Azure Pipelines and Pagure have no other common points for integration.

From my perspective, I'm ok with one namespace for all these projects and it would probably be better to have it separate.

From my perspective, I'm ok with one namespace for all these projects and it would probably be better to have it separate.

Got it
Thank you :)

I do not know enough to give an answer beyond what the ticket opener wants. So let us try 1 namespace and have it separate from fedora-infra.

If you want to have a namespace name, something like 'idm' (identity management) would be good. This would allow us to use the same namespace to other related projects going forward.

@bstinson can you (or have you already) processed this?

@bstinson can you (or have you already) processed this?

Hi @kevin,
I can take this now!
we have deployed new cluster and I can create them a namespace in there.
as suggested by @abbra , I will create a namespace called idm and will assign them as the namespace admins.

@abbra, hey, to be able to login to cluster, you will need an ACO username (accounts.centos.org)
can you please create one if you don't have, and send then email address to me in dm/here/email.
I will be able to create the namespace the same day as you provide me the info, sorry for the delay so far

Metadata Update from @siddharthvipul1:
- Issue assigned to siddharthvipul1

3 years ago

@abbra
a better way would be to drop me an email with

* namespace_name:
* namespace_admins:
 - list of admins' ACO email address

You can see my email address in my FAS account

@siddharthvipul1 my ACO username is the same (abbra).

@siddharthvipul1 my ACO username is the same (abbra).

I would need the email address :(

I sent you an email.

namespace created, and @abbra has been added as the namespace admin.

@abbra
You can login to the cluster on: https://console-openshift-console.apps.ocp.ci.centos.org/dashboards
and your jenkins deployment is: https://jenkins-idm.apps.ocp.ci.centos.org/

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

3 years ago

Confirmed: I was able to login to OCP and to the deployed Jenkins system.

Thank you!

Login to comment on this ticket.

Metadata