Jenkins is broken

[Matthias Vogelgesang]

Browsing the management page of Jenkins (​http://ufo.kit.edu/jenkins/manage) reveals serious problems, one of them being, that you cannot add new CMake-based projects. The "solution" page is at ​https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken but doesn't really tell me how I could fix this.

So I guess it has something to do with the way we integrate Jenkins (running on ipepdvcompute1) and the URLs pointing to it (ufo.kit.edu). For example, the main page ​http://ufo.kit.edu/jenkins is correctly forwarded.

[Suren A. Chilingaryan]

The reverse proxy is actually configured. Using the specified test page, you can see, the location header is rewritten as they want:

$ curl -D - http://ufo.kit.edu/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test
HTTP/1.0 302 Moved Temporarily
Date: Tue, 07 Feb 2012 09:17:05 GMT
Server: Winstone Servlet Engine v0.9.10
Location: http://ufo.kit.edu/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test-for-reverse-proxy-setup
Content-Length: 0
X-Powered-By: Servlet/2.5 (Winstone/0.9.10)
Content-Type: text/plain
X-Cache: MISS from iwr-proxy3.fzk.de
Proxy-Connection: keep-alive

Also, As I can see, all jenkins pages are displayed correctly. Is there anything really broken? Otherwise, I'd assume the bug is in the jenkins problem detection code :)

[Matthias Vogelgesang]

Try this: ​http://ufo.kit.edu/jenkins.

[Suren A. Chilingaryan]

You need a slash in the end. It was always like this. If for some reason now you need URL without slash, let me know and I'll configure this.

[Suren A. Chilingaryan]

OK. The problem is HTML rewrite engine is not able to catch all semi-absolute URLs produced by jenkins. This things are failing:

<input value="Test" onclick="validateButton('/descriptorByName/hudson.security.PAMSecurityRealm/test','',this)"

Generally, there is nothing I can do about this. The possible ways to work-around:

1. Custom HTML rewrite scripts may be written. But this a lot of work and I'll not go to do it unless extremely necessary.
2. The problem will not introduce itself if the direct domain name is used instead of "​http://ufo.kit.edu/jenkins". For instance, ​http://jenkins.ufo.kit.edu will do, but this takes some amount of bureaucracy. On over hand, I can easily set ​http://jenkins.suren.me.
3. The non-administrative part looks to work fine. For administration, the direct URL ​http://ipepdvcompute1.ka.fzk.de:8080 may be used.