Config.xml of the job gets lost/deleted randomly on jenkins. The issue is popping up in between while the job is running . Does anyone face such issue?
Related
Jenkins builds suddenly disappears from the jenkins UI for certain Jobs. The Job triggers and it can been seen in the ui but suddenly vanishes. The build is present in the master machine.
Has anyone faced this before. If so your insights will be really helpful.
We also saw some of our build history being missing when checked in the master all the builds were still present but there was a problem with symlinks being broken in the builds folder for a job
lastFailedbuild, Lastsatblebuild were reset to -1 even though there were some failed builds present.
But this got resolved once a few plugins(disk usage and metrics-diskusage) that were disabled were re-enabled and a reload configuration were done.
I have my all my jobs configurations present in the Jobs folder inside Jenkins folder. In the same way, projects are present inside the Workspace folder. But, the jobs are not showing up on Jenkins dashboard.
Previously all the jobs were showing up, but after upgrading Jenkins, I am facing this issue.
I have added the build flow job with my multijob.
I faced some issues with build flow job. It always executes twice whenever I gave build.
Is there anybody faced and solved this issue previously?
Today morning, we noticed all Putty Jobs running Jenkins were closed due to Network Issue. Once network was up, we re-started Jenkins and we observed that Jenkins Dashboard was not showing ANY jobs. We had around 80 Jobs on the dash board. We are using VM servers for Master/Slave setup. Config.xml is fine. What do we do? how do we get back on track?
All the jenkins jobs are basically xml config files kept in jenkins home.
If your Jenkins is not showing these jobs then it is not using same home directory.
Kindly check jenkins process to see which directory it is pointing to.
In the job post build action, am archiving the artifacts. 90% of the time, when the jenkins job reaches this step, the slave on which it is running hangs (or) goes offline (or) the job hangs and if I kill the job it throws a "Caused by: java.lang.OutOfMemoryError: Java heap space" error.
Am running Jenkins ver 1.560.
Has anyone seen this or is aware of a fix for this? Any help is appreciated.
Thanks
It looks like you're running into https://issues.jenkins-ci.org/browse/JENKINS-22734 which started in version 1.560 and will be fixed in 1.563.
It's always a good idea to browse the Jenkins change log, especially the Community Ratings section, when you install a new version.
Whenever Hudson master will run out of space, slaves will disconnect and will have to be restarted.
You need to check Hudson master box and see how much space is allocated to the drive where hudson is running.
Another thing to note is that even if a job is running on slave, artifacts are archived always on master. So space allocation on master should be done properly.
I ran into this issue with 1.560v of Jenkins. Right now I have disabled the archiving of the maven artifacts from the "Build" section.