Description of problem: jenkins seems broken out of the box with a missing class error. $ cd /usr/share/jenkins/webroot/WEB-INF/lib $ java -jar jenkins-core-1.609.jar Exception in thread "main" java.lang.NoClassDefFoundError: hudson/remoting/Callable at hudson.Main.getHudsonHome(Main.java:77) at hudson.Main.run(Main.java:63) at hudson.Main.main(Main.java:55) Caused by: java.lang.ClassNotFoundException: hudson.remoting.Callable at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 3 more That missing class is provided by remoting.jar in the same directory. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to James Patterson from comment #0) > $ java -jar jenkins-core-1.609.jar Running Jenkins this way is not supported in Fedora. The recommended way to run Jenkins is using systemd: systemctl start jenkins systemctl stop jenkins
The above is not my problem, it's the reproducer for the actual bug: monitoring external jobs is not possible. Docs: https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs See "Monitoring an execution" Seems it's broken on Fedora.
Then please describe the actual problem you are having.
Using any combination of the jenkins-core*jar files, I always get the traceback from comment 1 while running the command for monitoring an execution from the jenkins wiki, i.e. $ sudo updatedb $ locate jenkins-core|grep jar$ For each of those results, I run: $ export JENKINS_HOME=http://user:pw@myserver.acme.org/path/to/jenkins/ $ java -jar foundpathandfile.jar "job name" <program arg1 arg2...> then the traceback from comment 1.
s/combination//;
Running Jenkins JAR directly is not supported in Fedora, but I think we can add a script for this purpose. Michal, do you agree?
Hi James, thanks for the bug report. The problem is caused by missing Class-Path entry in MANIFEST.MF of our jenkins-core.jar. Having Class-Path in MANIFEST.MF is banned by packaging guidelines in Fedora. It's a bit unfortunate, but as Mikolaj suggested, we can add script for this purpose.
That sounds great. Would it be possible to get a copy of this script to test?
I will prepare it later today/tomorrow and push it as an update for Fedora 22. It will be available for testing via fedora-updates-testing repository, or directly downloadable from http://koji.fedoraproject.org/koji/.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.