I asked on Slack #asfinfra .  Apparently Jenkins was upgraded and they are
working through various issues.  This need for auth is not intentional;
it's a temporary glitch.  Seems to be working now.

On Fri, Mar 13, 2026 at 5:20 PM Chris Hostetter <[email protected]>
wrote:

>
> : Earlier the Apache Solr and Lucene CI was publicly accessible and we
> : used to monitor the s390x builds. Recently it seems to require
> : credentials, so we can't see the s390x jobs anymore.
>
> I was a little confused by your message -- but poking around a bit it
> seems like you are specifically refering to the jobs running on
> ci-builds.apache.org -- which AFAIK shouldn't intentionally require any
> authentication.
>
> Based on my logs, RSS feeds from ci-builds.apache.org seem to have
> stopped
> working ~ March-8th. (But jenkins jobs citing ci-builds.a.o URLs have
> still been sending results emails since then)
>
>
> Currently requesting any "https://ci-builds.apache.org/..."; URLs now seem
> to respond with a 403 and an HTML body that includes a javascript based
> redirect to "/securityRealm/commenceLogin?from=..." ... and loading *that*
> URL generates a 302 redirect to
> "https://jenkins-ccos.apache.org/operations-center-openid/authenticate?...
> ."
>
> https://jenkins-ccos.apache.org/ does not seem to require any
> authentication -- but it also doesn't seem to be hosting any Lucene/Solr
> jobs: just jobs that seem related to backups.
>
>
> Even weirder: ci-builds.a.o and jenkins-ccos.a.o resolve to completley
> differnet IP#, So i'm not really sure what's going on with that redirect.
> This doesn't seem like a missconfiguration, this seems very intentional?
> ... but also ... bizare?
>
>
> Ultimately: This is a question for ASF INFRA ... I have no clue WTF is
> going on, but I am also about to go offline for a week, so someone else
> in the project is going to have to follow up.
>
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to