I tried to update Jenkins to the latest LTS version since the version we were using had some non-critical UI errors (https://issues.jenkins.io/browse/JENKINS-69627) that were preventing me from easily giving administrator privileges to new accounts. The newer versions of Jenkins does not support Java 8 (which is the default version of Java on Sherlock) so I had to edit the shell script we use to fire up a Jenkins task /home/groups/mcovert/usr/local/bin/jenkins_job.sh to load modules for newer versions of Java (11 or 17). Running Jenkins with the new Java versions led to this reported error (https://stackoverflow.com/questions/68490185/trying-to-install-startup-jenkins-in-ubuntu-server-hudson-util-awtproblem) which I wasn't able to resolve on Sherlock. I tried installing fontconfig to $GROUP_HOME but this did not resolve the issue. I ended up updating Jenkins to the latest version that supports Java 8 instead (2.346.1), which still has the same UI errors.
I was be able to use a workaround to add @rjuenemann as an admin, so I don't think this is something that we'll need to resolve urgently. Though we might need to eventually update Jenkins as things get deprecated and more issues arise.
I tried to update Jenkins to the latest LTS version since the version we were using had some non-critical UI errors (https://issues.jenkins.io/browse/JENKINS-69627) that were preventing me from easily giving administrator privileges to new accounts. The newer versions of Jenkins does not support Java 8 (which is the default version of Java on Sherlock) so I had to edit the shell script we use to fire up a Jenkins task
/home/groups/mcovert/usr/local/bin/jenkins_job.sh
to load modules for newer versions of Java (11 or 17). Running Jenkins with the new Java versions led to this reported error (https://stackoverflow.com/questions/68490185/trying-to-install-startup-jenkins-in-ubuntu-server-hudson-util-awtproblem) which I wasn't able to resolve on Sherlock. I tried installingfontconfig
to$GROUP_HOME
but this did not resolve the issue. I ended up updating Jenkins to the latest version that supports Java 8 instead (2.346.1), which still has the same UI errors.I was be able to use a workaround to add @rjuenemann as an admin, so I don't think this is something that we'll need to resolve urgently. Though we might need to eventually update Jenkins as things get deprecated and more issues arise.