Add SSO support for Jenkins in the service Mojo spec

Bug #1419722 reported by Caio Begotti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Capomastro
Confirmed
Medium
Unassigned

Bug Description

The current Mojo spec deployment of Capomastro will not expose its Jenkins unit, but there might exist situations in which it would be interesting to expose Jenkins (for when we need to manually patch the XML config of a project). IS maintains ci.admin.canonical.com with a neat SSO support that we could use. Apparently artifacts exposed to unauthenticated users would not be a problem anymore as the whole site is behind SSO. Also, in case of an archiver failure in Capomastro there is still a way to get artifacts out of the service.

Revision history for this message
Daniel Manrique (roadmr) wrote :

Can Capomastro access Jenkins behind SSO, or would it have a way to hit some sort of private address to avoid needing this?

This is a great idea but sounds like a larger feature and may involve mostly charming and spec work. I'll set for future for the time being.

Changed in capomastro:
milestone: none → future
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.