I have installed thinBackup plugin to back up my Jenkins, and I have configured it as follows:
So, there should be a full backup everyday after 08:00 PM, unfortunately for some reason, the scheduled backups are not running at all.
But, manual backup (by clicking the Backup Now button in the main page) works:
Jenkins has write access to the backup directory.
Can anyone let me know what could be the problem here?
FYI: I got the same problem with Periodic Backup plugin as well.
Thanks in advance.
I faced the same problem, restarting Jenkins worked for me.
Related
I Installed locally Jenkins 2.224 using war file.
I am trying to set a job to pull files from git as on the screenshot below.
but when I save my job and then click configure again - None radiobutton is selected and all git settings are lost. Did it happen to anyone else? I cannot find what is the reason for this issue.
This is a bug in v2.224 that has been fixed in the subsequent version. Upgrading to the latest version should fix your issue.
It is taking too much time (waiting from last hours). I have only 1 project with multiple jobs. I have updated plugings regarind security issues and few updatest no luck. I have restarted jenkins many times and worked fine but now it stucks. Is there any way out to kill/suspend jenkins to avoid this wait
After lot of reserach, I did not find any answer. So best way is to go to the jenkins folder in the drive, navigate to plugins directory and remove the folder which are installed and updated on the current date. Then strat teh jenkins and download the plugins which are deleted from the plugins folder
I am using Jenkins v1.651.3 and to schedule automated daily backup I have installed the ThinBackup plugin v1.9. But when I trigger backup manually it does not work. In the system logs all I can see is -
Sep 01, 2017 9:31:37 AM INFO org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink doBackupManual
Starting manual backup.
Sometimes the backup process doesn't take place because of the directory permission issue.
Make sure that your Jenkins user has the write permission to the directory where you are trying to create your backup.
I have had a similar issue like this, and in my case was as simple as the Backup directory was not correctly set or empty. If this settings of the ThinBackup is not set, when you launch it manually it does nothing, and no error at all is shown. After set a correct path, it works normally. Then my advise is to check your settings to see if something is wrong.
Thanks, #ANIL his answer saves my day.
Previously I backup Jenkins to a mount folder, but it doesn't work recently. so I use user
jenkins to log in on the Jenkins server then try the below commands
cd $BACKUP_FOLDER
bash: cd: data: Stale file handle
My jenkins user can't access this directory, but I personal user can. But anyway, this problem is caused by permission.
I created a slave node and ran a pipeline successfully but after that unable to configure the node. I've tried restarting Jenkins using the weburl as well as the shell. At this point, its stuck at creating a new Node or even when configure is clicked. The page just never opens. Deleting an existing node worked however.
Even the Mutli-Slave config plugin runs into the same problem. I'm guessing some data corruption? It would be a shame to reinstall Jenkins and redo the awful amount of configuration. Any ideas?
I was just beginning to like Jenkins.
PS: Editing the master node works. Using Jenkins 2.5.
EDIT:
I manually created a folder for a node under JENKINS_HOME/nodes and copied a config.xml for the node from some other server. The node appears in the list after server restart but still the option to Configure it hangs forever.
After wasting a lot of time I finally fixed the issue by downgrading Credentials plugin to the previous version: 1.28. Earlier today I had upgraded to the available latest 2.0.
Looks like others also hit the same problem today: https://github.com/jenkinsci/credentials-plugin/issues/49
I am facing a weird issue after upgrading jenkins to 1.632. After upgrade I am not able to see the build history in jenkins and surprise thing is that history is lost for few jobs. I have reverted back the jenkins but still I am not able to see the history. To make this issue more clear I am running Jenkins on tomcat and I just replace the jenkins.war file in webapps directory. I believe it should not have any impact on JENKINS_HOME location. Is there any way to restore the build history? BTW I also tried the option "reload configuration from the disk" but that is also not working. I am running jenkins on Linux box.
Any kind of help is highly appreciated.
Thanks,
Sanjiv