# systemctl status jenkins
jenkins.service - LSB: Jenkins continuous build server
Loaded: loaded (/etc/rc.d/init.d/jenkins)
Active: active (exited) since Tue 2016-11-15 17:12:33 JST; 3min 58s ago
I am upgrading jenkins from 1.6 to 2.x but after replacing war file I can not start jenkins that can be seen above.
I would recommend to download the 1.6 and run it to validate all remain the same and still workable. Probably you have some plugins that not supported (or should be upgraded to be supported) in versions 2+.
Related
We have recently upgraded Jenkins 2.365 for which we are using openJDK-11.
But, we are still using JDK8 to build and execute the test, I want to attach the node of RHEL machine with JDK8
Won't it possible with latest Jenkins i.e. version 2.365 releases?
I am in the process of upgrading jenkins server to latest LTS version (2.204.2 to 2.251.2) in my current work environment.
In present scenario jenkins installation and configuration is an automated process via chef.
The problem starts here :
i need to upgrade my jenkins server to latest LTS version via chef cookbook
remoting option has been obsolete in latest jenkins version
my present cookbook uses jenkins_script resource (using jenkins 6.0 cookbook from supermarket) to run groovy scripts
i am able to upgrade my jenkins server but unable to execute groovy scripts via jenkins-cli, its picking remoting option all the time and failing even though its obsolete in latest version
Is there any automated way to change protocol from remoting to ssh/http when chef client runs
.
Any valuable inputs will be helpful
I was using Jenkins 1.7.4 version in RHEL Linux server. I can able to configure the slave using "launch agent via execution of command on the master" option during slave setup.
Now we have upgraded jenkins to 2.121.1 version. Now we unable to find that option in the upgraded version.
How to fix this issue.
Manually I Installed command-launcher, jdk-tools plugin. Then it works.
I was able to install and run jenkins on my linux subsystem in Windows 10.
It listens on 8082.
But unfortunately, for an unknown reason, it hangs up infinitely after a few minutes (or to be precise after a I've made a change in a job config and execute a build).
Then, I checked in the terminal:
root#jup1t3r /h/navds# service jenkins status
Correct java version found
2 instances of jenkins are running at the moment
but the pidfile /var/run/jenkins/jenkins.pid is missing
root#jup1t3r /h/navds# service jenkins stop
Correct java version found
* Stopping Jenkins Automation Server jenkins
...done.
root#jup1t3r /h/navds# service jenkins status
Correct java version found
2 instances of jenkins are running at the moment
but the pidfile /var/run/jenkins/jenkins.pid is missing
So there is no way to stop Jenkins. How can I restart it ?
Getting below error in Jenkins during the last step of creating pipeline from github using personal access token -
Sep 03, 2017 7:34:43 AM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocol
INFO: ALPN callback dropped: SPDY and HTTP/2 are disabled. Is alpn-boot on the boot class path?
Jenkins ver. 2.78
openjdk version "1.8.0_141"
I am running jenkins using vagrant inside CentOS 7.
It worked fine after changing my machine from Mac OS to Ubuntu & upgrading the blueocean plugin to "1.3.0-beta-2".
The reason could be proxy or some other setting which was not allowing the communication to happen.
Since it took fair amount to time to debug, I hope someone else doesn't waste their time & check their machine configs before putting a bug.