I've installed Docker 2.4 quite some time ago using Chocolatey (my OS is Win 10). Since updating Docker using choco upgrade all always failed, I did the updates manually via the Docker itself (right-click → Check for Updates → etc.). Now I'm on version 3.2.
Since I want to get rid of this manual update process, I wanted to uninstall Docker from Chocolatey. But executing choco uninstall docker-desktop fails with ERROR: Exception calling "GetFullPath" with "1" argument(s): "Illegal characters in path.".
Of course, I could uninstall Docker the usual Windows way. But how would I remove Docker from Chocolatey so that I can do a fresh install?
I was able to solve the issue by manually uninstalling Docker with default Windows tools.
Afterwards, I deleted the folder C:\ProgramData\chocolatey\lib\docker-desktop. This resulted in a clean environment when it comes to Docker, because Chocolatey seems to maintain all package-related things in the corresponding C:\ProgramData\chocolatey\lib\<<package>> folder.
Finally, I could install Docker again via choco install docker-desktop.
I am able to install the Jenkins on the Ubuntu 18.04 machine.
After installation i am able to launch the GUI successfully... When I try
to install any plugin it says:
An error occurred during installation: No such plugin: cloudbees-folder
I tried restarting and tried installing on different Ubuntu server,but i am facing the same issue.
Can any body help me in resolving the issue:
Tried restarting the Jenkins.
Tried re-installing the Jenkins on fresh Ubuntu server.
finally i got my raspberry pi 3. I installed jenkins via
sudo apt-get install jenkins
sudo /etc/init.d/jenkins start
After the installation, I was able to connect to the server (localhost: 8080). Now i wanted to configure the Jenkins with new build jobs, but i realized i need to get the new Version (Jenkins 2). I downloaded the new .war-File from
wget http://updates.jenkins-ci.org/download/war/2.32.2/jenkins.war
and replaced it with the old one in /usr/share/jenkins
After
sudo /etc/init.d/jenkins restart
and connect to localhost:8080 i got no response. If i replaced the original .war-file i can connect to localhost:8080 (version 1.5).
I have already restarted my raspberry pi.
What am I doing wrong?
Now i solved the problem:
The downloaded .war-File was correct. I don't know why, but if i replace the war file it doesn't work.
simple solution:
java -jar jenkins.war --httpPort=
of the new .war-file and it works.
I installed Jenkins' Gradle plugin and used the automatic restart option via the Jenkins web interface. Jenkins seemed to hang on the "restarting..." page, so I finally tried to manually restart the Jenkins service on the server (64-bit Debian 7) using service jenkins restart.
Now, Jenkins is no longer running at all (verified with ps -ef | grep -i [J]enkins and service jenkins status), and when I try service jenkins [re]start, I see an [ ok ] message but nothing else seems to happen. I've deleted /var/log/jenkins/jenkins.log, and each time I try a service start (or restart), the log file reappears, but it's blank (ls -lA shows that the file was recently made, but cat produces no output). I also tried rebooting the server, with no effect. I finally deleted the Gradle folders under /var/lib/jenkins/plugins, which also did not appear to make a difference.
How do I even begin to approach this problem? Should I just re-install Jenkins?
EDIT: System info:
> uname -a
Linux AUC-Workstation1 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u1 x86_64 GNU/Linux
According to dpkg -l, I'm using Debian's jenkins package, version 1.617.
EDIT 2: I'm actually using the jenkins package provided directly by Jenkins, as per the instructions here.
I just had a problem where multiple Jenkins plugins were breaking Jenkins startup (after an upgrade) and here is the procedure I followed to resolve the issue, which might work for other plugin startup issues.
I'm working on an Ubuntu server, but I expect that this would work for Debian if it's going to work at all - I encourage others to adjust the procedure:
logged into the server and switched to the jenkins user (sudo su jenkins in my case)
went to the main jenkins directory
renamed plugins to plugins.problems_YYYYMMDD
previously, I attempted to disable the plugins, but this did not work for me (system still would not start)
created an empty directory plugins
restarted jenkins (sudo service jenkins restart)
In my case, this started just fine
iteratively followed the following procedure to add plugins back in
copied 1 or more plugins from plugins.problems_YYYYMMDD/ to plugins/
restarted jenkins
went to the plugin center and installed updates as available
sometimes I needed to install updates in a particular order due to dependencies
evaluated results in 'Manage Old Data'
I think I'm facing some manual updates of the old data
Note: if you know which plugins are likely the problem, then it is easier to just disable or temporarily (re)move them rather than (re)moving all of the plugins!
I never did figure out the initial problem, but I did get Jenkins working again, sort of.
I uninstalled Jenkins (using apt-get purge) and then re-installed it. This time it failed to start because it needed Java 7, but I apparently only had Java 6 installed (this surprised me, because I thought I had previously configured Jenkins to use Java 7 on that machine). So I installed openjdk-7-jdk and openjdk-7-jre, set JAVA and JAVA_HOME appropriately in the Jenkins config file, and started the service again. This allowed Jenkins to start.
I am trying to install Jenkins 1.504 on a CentOS 6.6 box. The script to set up the jenkins service attempts to run /etc/rc.status but that file does not exist. I installed from an RPM that was given to me (the box is a standalone machine.) I understand that rc.status is typically associated with the SUSE distro. Do I just have the wrong RPM, or is there a way I can get this set up on CentOS?