[JIRA] [ghprb] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Frank K updated JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Any clues why this is happening Honza Brázdil Valdis Rigdon? Change By: Frank K (07/Jul/14 10:41 AM) Component/s: ghprb Component/s: github This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Frank K created JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Issue Type: Bug Assignee: Unassigned Components: github Created: 01/Jul/14 1:21 PM Description: GitHubCommitNotifier is throwing a (very helpful) exception which causes the build to fail. This started this morning without things being changed on our end. At first I thought it was due to the upgrade to 1.570 but even after downgrading to 1.569 it did not resolve the issue. The exception that is being thrown in the console is: 15:09:57 Publishing Clover coverage report... 15:09:57 Publishing Clover XML report... 15:09:57 Publishing Clover coverage results... 15:09:57 Recording test results 15:09:58 ERROR: Publisher com.cloudbees.jenkins.GitHubCommitNotifier aborted due to exception 15:09:58 java.lang.NullPointerException 15:09:58 at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:53) 15:09:58 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 15:09:58 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) 15:09:58 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736) 15:09:58 at hudson.model.Build$BuildExecution.post2(Build.java:183) 15:09:58 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685) 15:09:58 at hudson.model.Run.execute(Run.java:1757) 15:09:58 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 15:09:58 at hudson.model.ResourceController.execute(ResourceController.java:88) 15:09:58 at hudson.model.Executor.run(Executor.java:234) Project: Jenkins Priority: Major Reporter: Frank K This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23202) RSS is not sorted by date
Frank K commented on JENKINS-23202 RSS is not sorted by date Ah, I see. I should use rssAll instead. But it does still make sense to have the latest built on top for rssLatest IMHO This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23202) RSS is not sorted by date
Frank K created JENKINS-23202 RSS is not sorted by date Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/May/14 12:12 PM Description: It appears that the RSS feeds (specifically rssLatest) are not ordered by date. This results in a latest feed with stuff from May and even January even though we had 100+ tests the past months. Project: Jenkins Labels: rss Priority: Minor Reporter: Frank K This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-22157) Web Hook Does not Start a build
Frank K commented on JENKINS-22157 Web Hook Does not Start a build We are seeing the exact same thing on our Jenkins environment. The "polling" system is not reliable so we switched to push (which is also more optimal api wise) only to run in to this particular issue which again results in jobs not being built when they should have been. Saving the configuration does "wake" it up again, something is pretty messed up here! The refspec is however set to +refs/pull/*:refs/remotes/origin/pr/* not sure if that matters here since it does match (and more). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive from time to time
Frank K commented on JENKINS-21677 Jenkins becomes unresponsive from time to time Starting up fresh also shows that the GUI has trouble responding. It shows the "Please wait while Jenkins is getting ready to work" message to one browser even though the plugins in the background seem to function (in this case I see IRC joins and parts). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive from time to time
Frank K edited a comment on JENKINS-21677 Jenkins becomes unresponsive from time to time Starting up fresh also shows that the GUI has trouble responding. It shows the "Please wait while Jenkins is getting ready to work" message to one browser even though the plugins in the background seem to function (in this case I see IRC joins and parts). It appears to be the dashboard, going straight to /login does show the login page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive from time to time
Frank K updated JENKINS-21677 Jenkins becomes unresponsive from time to time Change By: Frank K (07/Feb/14 11:57 AM) Summary: Jenkinsbecomesunresponsive aftersaving(job)settings fromtimetotime Description: WeareexperiencingseriousissueswithourJenkinssetup.Thesetupconsistsofonemaster(2core, 2GB 3GB )andtwoslaves( 8core 6core , 8GB 6GB )connectedviaSSH.Ifsomeonesavesasetting-eitherglobalorajobone-Jenkinsbecomesunresponsive.Thesavingpagekeepsonloadinggenerallyandthedashboardbecomesunavailable.Somesubpagesstillworkstrangely.Afteraperiodoftimethewebinterfaceworksagain,butthisvariesfrom5to30minutesandisnotacceptablebehaviour.Wedohavequiteafewpluginsinstalled(somegotaddedasdependencytoanother):*ansicolor*antplugin*checkstyleplug-in*chucknorrisplugin*credentialsplugin*duplicatecodescannerplugin*externalmonitorjobtypeplugin*gitclientplugin*githubapiplugin*githubplugin*githubpullrequestsbuilder*greenballs*htmlpublisherplugin*javadocplugin*jenkinsactivedirectoryplugin*jenkinscloverplugin*jenkinsemailextensionplugin*jenkinsexclusionplugin*jenkinsgitplugin*jenkinsgravatarplugin*jenkinsinstant-messagingplugin*jenkinsircplugin*jenkinsjdependplugin*jenkinsJIRAplugin*jenkinsjQueryplugin*jenkinsmailerplugin*jenkinsnotificationplugin*jenkinsphingplugin*jenkinspost-buildscriptplug-in*jenkinssonarplugin*jenkinsviolationsplugin*jobimportplugin*LDAPplugin*Matrixauthorizationstrategyplugin*Mavenintegrationplugin*PAMauthenticationplugin*Performanceplugin*Plotplugin*PMDPlug-in*SCMAPIPlugin*SimpleThemePlugin*SSHAgentPlugin*SSHcredentialsPlugin*SSHslavesplugin*StaticAnalysisCollectorPlugin*StaticAnalysisUtillities*Subversionplugin*Templateprojectplugin*Timestamper*Tokenmacroplugin*warningsplug-in*xUnitPluginAllourpluginsarethelatestversion.Ifyouneedanymoreinformationorhaveanypointerstowherethisissuecanbeoriginatingfromthatwouldbeveryhelpful. Thisnotonlyaffectstheguibutprocessing/cronsetcareallstopped(e.g.GHPRBdoesntrun,periodicbuildsarentexecuted) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive from time to time
Frank K commented on JENKINS-21677 Jenkins becomes unresponsive from time to time The logging on finest doesn't provide much valuable information. It is not only the GUI that becomes unavailable, it also is the whole internal processing (e.g. no GitHub pull requests being built, no periodic building of jobs) Would switching to Tomcat help? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-21680) SimpleHttpConnectionManager being used incorrectly
Frank K created JENKINS-21680 SimpleHttpConnectionManager being used incorrectly Issue Type: Bug Assignee: Honza Brázdil Components: ghprb Created: 06/Feb/14 8:04 AM Description: It appears that this plugin is using SimpleHttpConnectionManager incorrectly, according to our Jenkins log: The following message appears (nearly) every minute in our Jenkins log: Feb 2, 2014 7:42:50 AM org.apache.commons.httpclient.SimpleHttpConnectionManager getConnectionWithTimeout WARNING: SimpleHttpConnectionManager being used incorrectly. Be sure that HttpMethod.releaseConnection() is always called and that only one thread and/or method is using this connection manager at a time. Since it has no prefix, I can't be sure this is indeed GHPRB but since this is the only thing that runs that often I assume it is. Project: Jenkins Priority: Major Reporter: Frank K This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive after saving (job) settings
Frank K commented on JENKINS-21677 Jenkins becomes unresponsive after saving (job) settings Any specific loggers I can/should add? Logging configuration is pretty annoying, you'll have to know all names.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive after saving (job) settings
Frank K created JENKINS-21677 Jenkins becomes unresponsive after saving (job) settings Issue Type: Bug Assignee: Unassigned Components: gui Created: 06/Feb/14 6:49 AM Description: We are experiencing serious issues with our Jenkins setup. The setup consists of one master (2core, 2GB) and two slaves (8core, 8GB) connected via SSH. If someone saves a setting - either global or a job one - Jenkins becomes unresponsive. The saving page keeps on loading generally and the dashboard becomes unavailable. Some subpages still work strangely. After a period of time the webinterface works again, but this varies from 5 to 30 minutes and is not acceptable behaviour. We do have quite a few plugins installed (some got added as dependency to another): ansicolor ant plugin checkstyle plug-in chucknorris plugin credentials plugin duplicate code scanner plugin external monitor job type plugin git client plugin github api plugin github plugin github pull requests builder green balls html publisher plugin javadoc plugin jenkins active directory plugin jenkins clover plugin jenkins email extension plugin jenkins exclusion plugin jenkins git plugin jenkins gravatar plugin jenkins instant-messaging plugin jenkins irc plugin jenkins jdepend plugin jenkins JIRA plugin jenkins jQuery plugin jenkins mailer plugin jenkins notification plugin jenkins phing plugin jenkins post-build script plug-in jenkins sonar plugin jenkins violations plugin job import plugin LDAP plugin Matrix authorization strategy plugin Maven integration plugin PAM authentication plugin Performance plugin Plot plugin PMD Plug-in SCM API Plugin Simple Theme Plugin SSH Agent Plugin SSH credentials Plugin SSH slaves plugin Static Analysis Collector Plugin Static Analysis Utillities Subversion plugin Template project plugin Timestamper Token macro plugin warnings plug-in xUnit Plugin All our plugins are the latest version. If you need any more information or have any pointers to where this issue can be originating from that would be very helpful. Environment: Ubuntu 12.04, Jenkins 1.549 on built-in webserver Project: Jenkins Priority: Blocker Reporter: Frank K This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive after saving (job) settings
Frank K commented on JENKINS-21677 Jenkins becomes unresponsive after saving (job) settings Could you tell me how I can do that? There isn't anything about this in /etc/default/jenkins or the config.xml. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive after saving (job) settings
Frank K updated JENKINS-21677 Jenkins becomes unresponsive after saving (job) settings Change By: Frank K (06/Feb/14 7:23 AM) Environment: Ubuntu12.04,Jenkins1.549onbuilt-inwebserver ,openjdk-6-jre-headless This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21677) Jenkins becomes unresponsive after saving (job) settings
Frank K commented on JENKINS-21677 Jenkins becomes unresponsive after saving (job) settings Uhh, I meant increasing logging level. The normal logs only have some warnings that are probably originating from GHPRB but since there is no prefix I can't be sure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [phing] (JENKINS-20835) calling phing long running targets spawns new phing processes endlessly
Frank K commented on JENKINS-20835 calling phing long running targets spawns new phing processes endlessly I have figured out why it is causing problems for us and resolved it. In our case it was because we configured a full path to the phing binary (which wasn't in the path). After adding the phing binary to the /usr/bin (via update-alternatives) and disabling the phing-path its working fine for our Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [phing] (JENKINS-20835) calling phing long running targets spawn new phing processes enlessly
Frank K commented on JENKINS-20835 calling phing long running targets spawn new phing processes enlessly I'm facing the very same issue on a fresly installed Jenkins on Ubuntu 12.04. Running Phing trough Jenkins results in a massive list of processes, a high load and unresponsive server. Running the exact same command manually on the commandline works just fine and only launches one process. This is quite a serious issue, I can't believe there hasn't been any response whatsoever in the past ~2 months since this issue has been reported! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [phing] (JENKINS-20835) calling phing long running targets spawn new phing processes enlessly
Frank K edited a comment on JENKINS-20835 calling phing long running targets spawn new phing processes enlessly I'm facing the very same issue on a freshly installed Jenkins on Ubuntu 12.04. Running Phing trough Jenkins results in a massive list of processes, a high load and unresponsive server. Running the exact same command manually on the commandline works just fine and only launches one process. This is quite a serious issue, I can't believe there hasn't been any response whatsoever in the past ~2 months since this issue has been reported! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Frank K commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Jenkins uses /tmp by default, tricky but shouldn't matter unless you have cleanup crons/scripts running. I have changed `/etc/default/jenkins` to point the tmp folder somewhere else (/var/lib/jenkins/tmp, /var/run/jenkins and even /opt/jenkins) but even then it loses the static assets (the whole 0.0.0.0--jetty unpacked war!) If I create the mentioned war folder Jenkins fails to even start. Strange stuff... TL;DR: This appears to be something else and not because its in the /tmp folder... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
