I've encountered a problem using the backup plugin.
I'm getting an error when trying to restore a previous backup using the backup plugin.
"Error copying backup files: Failed setLastModified on /var/lib/jenkins_restore.
I ran "chmod -R 777 /var/lib" to solve a previous problem which that was the only solution.
Would appreciate your help!
Thanks in advance.
Related
when i tried to restart manually it say Jenkins cannot restart itself as currently configured.
As i cant restart it I am unable to update the plugins .
I tried to uninstall extra plugins but i was unable to resolve it .
could you guys explain how to resolve it so that i can create and run jobs .
I don't think those warnings are a blocker to run a job.
If you can't update the plugins you can try to update the jenkins biany/image itself.
We are using advanced installer 9.7 .
We are using Jenkins to create builds but we are facing the below issue with jenkins plug in-
I tried all online resources but had no luck please help to fix this.
Running as SYSTEM
Building on master in workspace D:\JenkinsWorkspaces\jobname
$ "C:\Program Files (x86)\Jenkins\tools\caphyon.jenkins.advinst.AdvinstInstallation\Advanced_Installer_-app\bin\x86\AdvancedInstaller.com" /Register ********
[jobname] $ "C:\Program Files (x86)\Jenkins\tools\caphyon.jenkins.advinst.AdvinstInstallation\Advanced_Installer-_app\bin\x86\AdvancedInstaller.com" /execute "C:\Source\Advanced Installer\projectname.aip" "D:\JenkinsWorkspaces\foldername\aic8583942971418633890aic"
In my case, adding the "clean" options when running the build, solved the issue.
I want to backup configuration of job, I am using to do this ThinBackup plugin in version 1.7.4 . And in every configuration of the job, there is something like Promote builds when.., how to backup this?
I ran into same issue and found this is an open bug. Looks to have a fix but a new version of the plugin hasn't been released.
A workaround which seems to work OK so far, is to separately backup the config.xml files under the JENKINS_HOME/jobs/. On Linux I ran the below from the Jenkins home directory to create this additional backup:
$ find jobs -name config.xml -exec tar -rzvf /tmp/config.xml-BACKUP.tgz {} \;
So I'm still using ThinBackup to get all the other bits but after restoring its backup:
tar -xzf /tmp/config.xml-BACKUP.tgz
I then restored the jobs config.xml backup and restarted Jenkins.
They are a some options with the ThinBackup plugin:
Did you try to enable the "Backup build archive" option?
First time I m facing this issue. When I try committing my project. I face issue like beloow
svn: Working copy '/Users/administrator/Documents/Checkout/Mar 26 6.23 pm/XXX.xcodeproj' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
My project is as noted as locked. What would be the issue? Tried in internet noting works out.
How can I remove locked state?
if I try clean SVN it shows error like
$svn cleanup
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: Working copy '/Users/administrator/Documents/Checkout/Mar 26 6.23 pm' is too old (format 10, created by Subversion 1.6)
sometimes when svn found the files inn working copy are not intended for committing to svn tool will lock such files and user have to release the lock before committing it.
i've setup my own jenkins buildserver today on my windows PC to build commits to my bitbucket.org-repository automatically.
Sadly i'm deep in trouble with the conenction between jenkins and git.
This is my Jenkis-Git configuration:
This is the Jobconfiguration:
If i now run "Build now" i'm getting the following output in console:
I hope somebody here is abled to help me with this problem. The Job is building... and building... and building... no result.
Kind regards,
Daniel
I get these Git-related warnings as well, but Jenkins is working just fine for me. I believe that they can be ignored. There is an open issue about this.
confirm you do indeed have Git installed on your system. try again.
If still having issue, you may need to also add the path of the Git executable to your Node configuration. By going to your Node configuration page, 'Node Properties' section, 'Tools Locations' setting. There you will find an option to explicitly add the path to Git.