Jenkins Job stuck in Uploading dSYM to Crittercism - jenkins

My Jenkins Job worked well, however, recently it usually stuck in
09:10:02 Archiving artifacts
09:10:05 Uploading dSYM to Crittercism...
09:10:06 /home/jenkins/.jenkins/jobs/JobName/builds/23/archive/build/artifacts/Glip-dSYM.zip
Loading .....
It always loading. And I can't stop it unless reboot my Jenkins master server.
My question is
1. How can I stop it unless reboot server?
2. How solve this problem always loading problem?
Thanks in advance.

It seems you are using Jenkins plugin to upload dSYM which is developed by a third party developer. You may refer to its documentation to see if it helps you :
https://wiki.jenkins-ci.org/display/JENKINS/Crittercism+dSYM+Plugin
Otherwise, post a comment underneath it as this seems to be related to Jenkins job and not Apteligent.

Related

What does the Jenkins iLmBjh process do?

Today I noticed that several of our Jenkins jobs (which are independant, different projects and everything) failed.I investigated an finally listed all processes on the machine that Jenkins uses with the top command. It showed me a very greedy process launched by Jenkins, which name is iLmBjh. Not very clear, isn't it?I tried some things and finally killed it. But it appeared again when I launched a new Jenkins job.Do someone know what this process does? It's the first time I see it on the processes list...
Ok, I guess I found the problem and it's kind of surprising. On our Jenkins instance, we had the JiraTestReporter plugin installed. Our Jira licence ended today. And when I checked the Jenkins logs, it was full of Jira error messages.What is disturbing is that we weren't using it at all... in any of our jobs!I uninstalled it and was able to run my job again. The iLmBjh process did not come back.

Jenkins plugin not showing up

probably a newbish question, but that's what I am. I need to run a post build script, so I installed the post-build-task plugin onto my Jenkins server (v2.5). For some reason, when I go to the job configuration page, there is no checkbox or anything for the plugin. Is there some common pitfall I am stepping into or something?
Edit: I have restarted the server.
So it was a blatantly simple issue. The job I was working in was a pipeline, and it needed to be a freestyle project.
Restarting will update the plugins..

Jenkins does not show changes from last build to latest build

I am currently seeing an issue in jenkins that even if there is a change in the build, it always says 'No changes from last build'(which is taken from perforce). And in the console output I see that mail is triggered to concerned people who have modified the file in the latest build.
Any Idea what could be the reason ?
Thanks in adv
Have you seen this issue reported on the Jenkins site: 'Polling builds project regardless of changes'?
Perhaps it is related to the issue you are having.

Jenkins Crashes after installing GitHub Plugin

I have a question about updating GitHub plugin.
Everytime I do an update plugin such as GitHub and restart the jenkins, Jenkins start crashing. when I try to access jenkins through URL in my browser, the error page shows up with some exception "class not found jenkins/model jenkins" . and then in order to make jenkins working again , I have to delete the plugin entirely from the plugins directory. I wish someone has an answer for this because I really need to make my github projects available to jenkins for build. Thanks
It is a very usual problem with Jenkins. My workaround was to either update the jenkins (where ever it is installed) and restarting the hudson service.
sometimes even restarting the service works.
often you might need to remove those plugins from within (/var/lib/hudson/plugins/) and restart the service.

jenkins missing jobs after removal of plugins

I have a Jenkins Server (1.510) on Win 2008 with ~100 jobs.
After installing and then uninstalling the CloudBees (Plugin_1, Plugin_2) set of plugins + restart I have the following issues:
half of the Jobs are now missing.
many plugins are not functioning well, for example the green-balls plugin is not working and also the entry to launch the backup plugin is missing
many built in Jenkins buttons such the new "Credentials" is missing from the "Jenkins Configure" Menu.
Looking at the FS, i still see all the jobs.
I already tried :
Using the reload configuration
Reinstalling the plugins
Reinstalling Jenkins with the same version once again
Still the jobs are missing
Any idea how to solve it?
Thanks,
Doron
When job is loaded, many of the related Java classes get instantiated. If instantiation fails, usually because some plugin has been removed and that class is no longer available at all, then the job is hidden.
I suspect you have accidentally removed some other plugin too.
Note: Before actually doing anything, take full backup! Easiest is to backup entire Jenkins folder, where the jobs, configuration etc reside.
Easiest solution might be to just install Jenkins from scratch, install the plugins you do need (see below for troubleshooting if you're missing some), then copy the jobs subfolder to the new Jenkins. It might be best to do any configuration under Manage Jenkins by hand, but you can also just try copying the related XML config files.
If you are missing a plugin and can't figure out which one, you should look at jenkins.out.log and jenkins.err.log log files and search for exceptions happening after Jenkins is started. That may give you a clue on what plugin you are missing.
You can also try editing the job XML files to remove build steps you identified from the exceptions (remember to take backups first!), then restart Jenkins or select Reload configuration from disk from Manage Jenkins page.
If not solved, but you find relevant-looking exceptions or something else interesting, please update the question with details.
After I upgraded Jenkins, one of my jobs disappeared. I found out that although my job directory still existed, the config.xml file inside had somehow gone missing.
I restored this file from a backup, after updating all the plugins that needed updating, and reloaded the configuration, and the job reappeared in Jenkins.

Resources