Bug#726489: jenkins: Provide directions on how to make it available on non-local IPs

[Olivier Berger]

Package: jenkins
Version: 1.509.2+dfsg-2
Severity: wishlist

Hi.

It is not exactly explicit how Jenkins can be accessed, once installed, i.e. localhost:8080, from reading the README.Debian.

However, this shouldn't be very hard to guess if one examines the running processes... nothing a casual admin should be blocked by. Still, making it explicit may be better, IMHO.

But besides this minor point, I think it would be quite useful to provide directions on how to configure it (or what must be added, like apache + mod_proxy) to make it available on a non-local IP.

Of course https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache may be useful, but there may be a better Debian way of doing things, which would be worth documenting in README.Debian.

Many thanks in advance.

Best regards,

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.10-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash