canonical-ci-engineering team mailing list archive

[Larry Works <larry.works@xxxxxxxxxxxxx>]

Greetings all,

The Jenkins instances d-jenkins and q-jenkins have been migrated to
OpenID/SSO authentication. With the migrations of m-jenkins, dmz-jenkins
and dev-jenkins yesterday this means that all of the Jenkins instances
internal to the CI lab are now using OpenID/SSO with the exception of
s-jenkins which will be migrated tomorrow.

One note I do need to relay for the connection to the various Jenkins'
is as follows: You will need to used the FQDN of the jenkins instance
when connecting/logging in. If you receive an error message similar to:

Unable to find an on-going OpenID session. Could it be that you have
multiple host names for your Jenkins and you started the authentication
in one host name and landed back on another? If so configure the correct
Jenkins root URL so that those two host names will be the same

You will need to ensure you are using the correct URL with FQDN (listed
below).
        http://d-jenkins.ubuntu-ci:8080
        http://q-jenkins.ubuntu-ci:8080
        http://m-jenkins.ubuntu-ci:8080
        http://drude.ubuntu-ci:8080 (I need to work with webops to get
this changed to http://dmz-jenkins.ubuntu-ci:8080)
        http://dev-jenkins.ubuntu-ci:8080
        http://s-jenkins.ubuntu-ci:8080 (this one will not be verified
until it is transitioned to OpenID/SSO tomorrow)

If you are using the correct URL with FQDN and still receiving the error
message listed above you may need to clear your browser cache and/or
connect using a private tab. As always feel free to ping me (or the
Vanguard if I'm not around) in #ci or #ubuntu-ci-eng.

~w