| Summary: | dev-util/jenkins-bin: jenkins.service unit using system java | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Samuel Bernardo <samuelbernardo.mail> |
| Component: | Current packages | Assignee: | Patrick Lauer <patrick> |
| Status: | UNCONFIRMED --- | ||
| Severity: | enhancement | CC: | graaff, jstein |
| Priority: | Normal | Keywords: | PullRequest |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://github.com/gentoo/gentoo/pull/24186 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Jenkins service only starts when systemd service type is "simple". I saw this approach to define jenkins.service where is possible to define the required environment variables to set the preferred java version to use with jenkins: https://aur.archlinux.org/cgit/aur.git/tree/jenkins.conf?h=jenkins-lts https://aur.archlinux.org/cgit/aur.git/tree/jenkins.service?h=jenkins-lts Created the following PR: https://github.com/gentoo/gentoo/pull/24186 |
As a suggestion, would be better to avoid defining in jenkins.service the ExecStart with /usr/bin/java, but instead use only java, so it can be override by PATH definition to use another java version if required. I just define a drop-in like the following, but doesn't work because is not possible to override ExecStart: [Service] Environment=JAVA_HOME=/usr/lib64/openjdk-11 Environment=JDK_HOME=/usr/lib64/openjdk-11 Environment=PATH=${JAVA_HOME}/bin/:${PATH} ExecStart=java ${JENKINS_JAVA_OPTIONS} ...