How about we ditch managing users by hand and use the Jenkins SSO plugin?
I just did some toying around on my test jenkins box and was able to grant anyone in ~canonical-ci-engineering administrator access.
The sticking point is that I'm not sure if that would play nicely with our Jenkins scripts that set up jobs. Anyone have an idea how we could deal with that?
On 09/26/2013 02:27 PM, Francis Ginther wrote:
There are two jenkins instances for upstream merger tasks. - http://10.97.2.10:8080/ This handles all ubuntu engineering projects, most of you already have logins here. If you are unable to login and configure a job or a slave node, let me know. If it falls over, hardware support is done by Rick and Larry. - http://91.189.93.70:8080/ This handles upstream merger for all the community core apps. I've updated with logins for most of the team, but haven't yet hit everyone. It is hosted from my canonistack account, so sadly if it falls over, I have to be the one to get it going again. I'm in the process of moving this to a shared role account so that the account details can be shared. Francis
-- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
