joshfrench
commented
15 years ago My first thought is, if your integration server is already behind authentication why bother making a project private?
That said, I'm deferring authorization to Integrity itself. If a request is authorized by whatever means Integrity acknowledges, private projects should in fact be displayed -- see line 4 of integritray.rb. I haven't delved too deeply into how Integrity handles basic HTTP auth, though; you'd have to ask the Integrity team how that works.
Did I understand your question right?
I'm wondering if it makes sense to expose private project results in the xml. We want our servers protected by basic auth, however we still want to be able to view the build status using CCMenu. This won't work even providing a url to CCMenu containing the basic auth (something like user:pass@server.com/projects.xml). Does this make sense?