Add packaging support for unix domain sockets

[minfrin]

• Add /run/jenkins path in systemd-tmpfiles as a home for the socket
• Support JENKINS_UNIX_DOMAIN_PATH variable to pass the socket path

Added to winstone: jenkinsci/winstone#346 / jenkinsci/winstone#345

Testing done

• jenkins.war from most recent master

• RPM created as follows:

WAR=/home/minfrin/jenkins.war MSI= BUILDENV=env/release.mk BRAND=branding/jenkins.mk make rpm

• /etc/sysconfig/jenkins modified for testing as follows:

JAVA_HOME=/etc/alternatives/jre_17

JENKINS_PORT=-1
JENKINS_PREFIX=/jenkins
JENKINS_UNIX_DOMAIN_PATH=/var/run/jenkins/jenkins.socket

Apache httpd configured as follows:

  ProxyPass unix:///run/jenkins/jenkins.socket|http://localhost/jenkins nocanon
  ProxyPassReverse unix:///run/jenkins/jenkins.socket|http://localhost/jenkins

Submitter checklist

Beta Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[timja]

Thanks!

[timja]

cc @kmartens27 / @MarkEWaite for changelog

[Artturin]

RuntimeDirectory="jenkins"

in jenkins.service should be a better fit here than a tmpfile.

[MarkEWaite]

in jenkins.service should be a better fit here than a tmpfile.

It is usually much more effective to submit a pull request with an explanation why a different location would be better. If you're not ready to submit a pull request, then an issue report is another way to start the conversation.

Commenting on a merged pull request is not nearly as likely to result in any action.