[JIRA] [core] (JENKINS-31559) All Jenkins jobs are automatically launched after the restart of the Jenkins instance
Title: Message Title Ludovic Vercruysse created an issue Jenkins / JENKINS-31559 All Jenkins jobs are automatically launched after the restart of the Jenkins instance Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Nov/15 9:16 AM Priority: Critical Reporter: Ludovic Vercruysse Dear, Regularly, we face an issue with one of our Jenkins instance (based on 1.596.3): we restart the Jenkins instance on a daily basis at 00:15am CEST, and regularly (once per week), *+all +*Jenkins jobs are automatically started just after the restart of the instance, even if there was no change in the source code repositories and even if the job is not triggered. We did not see any specific message in the logs of our instance, which could allow us to have more information about this issue. Could you please provide us some help on this issue ? Best regards Add Comment
[JIRA] [core] (JENKINS-27663) Bad execution time for jobs periodically executed
Title: Message Title Ludovic Vercruysse closed an issue as Fixed We were facing performance issues on an internal instance of one of our source code repositories. Solving it solved exactly at the same time the timer issues on Jenkins. It makes me think that some Jenkins threads were trying to access to this source code repository and did not get any proper response which could have had impacted the Jenkins triggers. Jenkins / JENKINS-27663 Bad execution time for jobs periodically executed Change By: Ludovic Vercruysse Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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,
[JIRA] [core] (JENKINS-31230) Jenkins job started by timer at an unexpected time
Title: Message Title Ludovic Vercruysse created an issue Jenkins / JENKINS-31230 Jenkins job started by timer at an unexpected time Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Oct/15 1:39 PM Priority: Major Reporter: Ludovic Vercruysse Dear, We are currently using Jenkins 1.596.3 and we have faced an issue with a job which was not started at the correct timestamp by the timer. The job is configured to be executed automatically on a daily basis at 7:30pm CEST. The job execution has been correctly triggered and the build has started at 7:30pm CEST, as expected. However, the logs of the build show the following error message: Looks like the node went offline during the build. Check the slave log for the details. FATAL: channel is already closed It seems that there has been a communication issue between our Jenkins master (hosted on a VM) and our Jenkins slave (a physical server) Therefore, the job has failed. At that time, we did not face any hardware issue on the servers. In the jenkins logs, except if I missed it, I did not find any reference of this communication issue, therefore, I cannot identify the root cause of this communication issue.
[JIRA] [core] (JENKINS-31228) Missing build status in the build history of several jobs
Title: Message Title Ludovic Vercruysse created an issue Jenkins / JENKINS-31228 Missing build status in the build history of several jobs Issue Type: Bug Assignee: Unassigned Attachments: missingBuildHistory.zip Components: core Created: 28/Oct/15 1:07 PM Priority: Major Reporter: Ludovic Vercruysse Dear, We are currently using Jenkins 1.596.3 and we are facing issues with several Jenkins jobs for which the status of several builds is missing in the job history. As an example, we have a job X for which the history displays the following build results: build 28 (job failed) build 27 (job failed) build 26 (job successfull) build 23 (job failed)
[JIRA] [gitlab-merge-request-jenkins] (JENKINS-29698) NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin
Title: Message Title Ludovic Vercruysse commented on JENKINS-29698 Re: NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin Hi Timothy Olshansky, Could you please provide an update ? Which solution could you propose ? Best regards Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-merge-request-jenkins] (JENKINS-29698) NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin
Title: Message Title Ludovic Vercruysse reopened an issue Hi Timothy Olshansky, hi Kanstantsin Shautsou, I read the comments in https://github.com/jenkinsci/gitlab-merge-request-builder-plugin/pull/1 and I find it very disappointing that a fix has been developed for this issue but cannot be proposed through the Jenkins update center because two people disagree on the ownership of the plugin. May I ask you to discuss again together about this issue and find a collaborative approach in which both of you would be identified as owners/maintainers of this plugin, in order to allow Jenkins users like me to get this fix ? Best regards Jenkins / JENKINS-29698 NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin Change By: Ludovic Vercruysse Resolution: Fixed Status: Resolved Reopened Assignee: Timothy Olshansky Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [gitlab-merge-request-jenkins] (JENKINS-29698) NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin
Title: Message Title Ludovic Vercruysse created an issue Jenkins / JENKINS-29698 NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin Issue Type: Bug Assignee: Unassigned Components: gitlab-merge-request-jenkins Created: 29/Jul/15 12:16 PM Priority: Blocker Reporter: Ludovic Vercruysse Dear, We are currently using Jenkins 1.596.3 with the Gitlab Merge Requests Builder plugin version 1.2.2. If we create a jenkins job which uses this plugin, and if we try to save the configuration of the job, we see a NPE: WARNING: org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run() failed for hudson.model.FreeStyleProject@37d513a0[MY_JOB] java.lang.NullPointerException at org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run(GitlabBuildTrigger.java:100) at hudson.triggers.Trigger.checkTriggers(Trigger.java:266) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExec
[JIRA] [greenballs-plugin] (JENKINS-28422) Jenkins is hanging after a restart (deadlock)
Title: Message Title Ludovic Vercruysse commented on JENKINS-28422 Re: Jenkins is hanging after a restart (deadlock) Dear, Could you please provide an update on my previous comment ? Could you please also tell if some changes are planned on the JQS Monitoring plugin ? Best regards Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [greenballs-plugin] (JENKINS-28422) Jenkins is hanging after a restart (deadlock)
Title: Message Title Ludovic Vercruysse commented on JENKINS-28422 Re: Jenkins is hanging after a restart (deadlock) Dear, Thanks for your help. We have taken into account the snapshot version enclosed to this ticket on our qualification environment and did not see any regression. However, there is no big volume on this environment; we will be able to check this in production. Could you please provide a final release for this plugin ? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27663) Bad execution time for jobs periodically executed
Ludovic Vercruysse commented on JENKINS-27663 Bad execution time for jobs periodically executed Dear, Could you please provide support on this issue ? Best regards 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-27663) Bad execution time for jobs periodically executed
Ludovic Vercruysse created JENKINS-27663 Bad execution time for jobs periodically executed Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Mar/15 7:44 AM Description: Dear, On our platform, we have 3 jenkins instances based on the LTS 1.596.1 On each of these 3 jenkins instances, I have created a free-style job which is periodically executed each 2 minutes. This job does nothing else (no checkout from a repository, no maven build, etc - this is the more basic job which can be done) On the first 2 jenkins instances, the job is well executed every 2 minutes. However, on the third one, it is randomly executed (more or less every 20 minutes). This makes me think that I have a configuration issue on my third jenkins instance. On 27/03, I have added some logs in the Jenkins administration panel and found the following stack trace: cron checking 3/27/15 4:49 AM whereas the date on the server was different: [www@MYSERVER ~]$ date Fri Mar 27 10:32:27 CET 2015 In order to allow me to investigate on this issue and identify the difference between my 3 servers, I would need to know if there is a configuration file or a specific directory which manages the date of the jenkins crontab. Could you please explain how the cron process works inside Jenkins ? Please note that our Jenkins instances use: user.timezone=Europe/Paris Best regards Project: Jenkins Priority: Major Reporter: Ludovic Vercruysse 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-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Ludovic Vercruysse commented on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Please find below remarks to your suggestions: RAM: we are currently updating the parameter -Xmx of our JVM to use -Xmx8192m (the server itself has 12 Gb of RAM), we will let you know if this has a positive impact Disk usage plugin: this plugin was previsouly disabled (as we were using Jenkins 1.509.4), but during the delivery process, it has been delivered again by mistake. That's why you see so many errors in the logs of yesterday, but none in the logs of today (I have disabled it yesterday evening). Fingerprinting: most of our projects are maven ones; as far as I have understood from fingerprinting, it is not possible to disable it for maven projects. Could you please translate "IIRC" ? I do not understand it. Discard unloadable data: could you please tell how to do this ? References to j.p.model.JobFailedTimeInfo#recordFailedTimeInfo: we are checking from which plugin this log comes (seems to be an history plugin) 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-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Ludovic Vercruysse commented on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Please find the bundle enclosed to this ticket. 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-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Ludovic Vercruysse updated JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Change By: Ludovic Vercruysse (13/Mar/15 10:48 AM) Attachment: support.zip 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-27379) Stability issues faced with Jenkins 1.580.3 due to blocked threads
Ludovic Vercruysse closed JENKINS-27379 as Cannot Reproduce Stability issues faced with Jenkins 1.580.3 due to blocked threads I close this ticket, as we have upgraded our version to the latest LTS 1.596.1. As we are still facing the same issue, another JIRA ticket has been created: JENKINS-27412 Follow-up will be done in JENKINS-27412. Change By: Ludovic Vercruysse (13/Mar/15 10:23 AM) Status: Resolved Closed 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-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Ludovic Vercruysse created JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Issue Type: Bug Assignee: Unassigned Attachments: threaddump_jenkins.txt Components: core Created: 13/Mar/15 10:21 AM Description: Dear, In the ticket https://issues.jenkins-ci.org/browse/JENKINS-27379, I mentioned that we were facing issues with our Jenkins instance (based on the previous LTS 1.580.3) and you advised us to upgrade our instances to the new LTS 1.596.1. This has been done yesterday, but we are still facing stability issues due to blocked threads. Could you please investigate, based on the threaddump enclosed to this ticket and advice us on what we could check / do ? Best regards Project: Jenkins Priority: Blocker Reporter: Ludovic Vercruysse 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-27379) Stability issues faced with Jenkins 1.580.3 due to blocked threads
Ludovic Vercruysse commented on JENKINS-27379 Stability issues faced with Jenkins 1.580.3 due to blocked threads FYI, we have upgraded our Jenkins instances to the latest LTS (1.596.1). We will now monitor their usage and let you know if we face the same issue with the LTS 1.596.1. 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-27379) Stability issues faced with Jenkins 1.580.3 due to blocked threads
Ludovic Vercruysse created JENKINS-27379 Stability issues faced with Jenkins 1.580.3 due to blocked threads Issue Type: Bug Assignee: Unassigned Attachments: threads.txt Components: core Created: 12/Mar/15 8:17 AM Description: Dear, After upgrading our Jenkins instance from Jenkins 1.509.4 to Jenkins 1.580.3 (identified as LTS). Following this upgrade, we are facing stability issues and need to restart our Jenkins instance once or twice per day (which has an important impact for the company) The heapdump enclosed to this ticket show that several threads remain blocked in the JVM. "Finalizer" daemon prio=8 tid=3 BLOCKED As a result, CPU usage is increasing and the JVM fails in an OutOfMemory. As short term action, we have already increased by 4Gb the RAM of the server, but of course, it does not solve the issue, it only reduces a bit the impact. Have you already identified this issue ? If yes, is there a fix ? In which release ? Best regards Project: Jenkins Priority: Blocker Reporter: Ludovic Vercruysse 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.
