[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title laurent gil edited a comment on JENKINS-60822 Re: can't parse argument number: changelog.url I have exactly the same issue with chrome configured with french regional settings. I changed Chrome regional setting to US english and it works. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204165.1579519195000.2667.1579521420311%40Atlassian.JIRA.
[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title laurent gil commented on JENKINS-60822 Re: can't parse argument number: changelog.url I have exactly the same issue with chrome configured with french regional settings. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204165.1579519195000.2657.1579521300259%40Atlassian.JIRA.
[JIRA] (JENKINS-59543) Unable to provision slaves due to network interface and subnet ID both being set
Title: Message Title laurent gil commented on JENKINS-59543 Re: Unable to provision slaves due to network interface and subnet ID both being set Thank you for the fix i just encounter the same issue in production. BTW, i can we introduce automatic test for this kind of issue in my pipeline ? Do you have a good framework ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202173.1569501392000.2815.1570479120408%40Atlassian.JIRA.
[JIRA] (JENKINS-56441) Threads in TIMED_WAITING causing build agents to hold on to completed tasks
Title: Message Title laurent gil closed an issue as Fixed We find a way to fix it, however we think there is a bug which prevent thread to wake up. Jenkins / JENKINS-56441 Threads in TIMED_WAITING causing build agents to hold on to completed tasks Change By: laurent gil Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Threads in TIMED_WAITING causing build agents to hold on to completed tasks
Title: Message Title laurent gil commented on JENKINS-56441 Re: Threads in TIMED_WAITING causing build agents to hold on to completed tasks We finally managed to find the root cause. We are using Github Enterprise which as a quota on the number of API request per hour per user. We increased the limit to 10K however the issue persists. What we find is that in decreasing the number of request made by Jenkins we no longer have the issue. After some investigations i think that the policy used to decrease the Jenkins activity depending on the quota is too agressive. Indeed we noticed some sleep thread with warning messages related with the quota whereas we had more than half of the quota available. In an other hand the slept thread never wake up so i think about a kind of deadlock into the code but as newbee i could not figure it out. Hope those information will help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Threads in TIMED_WAITING causing build agents to hold on to completed tasks
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Threads in TIMED_WAITING causing build agents to hold on to completed tasks Change By: laurent gil Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached.Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out.*Jenkins Version:* 2.150.3 *Plugins:* [^jenkins-plugins.txt]*^Java version:^* ^openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode)^May be related with / JENKINS-56480Regards Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Threads in TIMED_WAITING causing build agents to hold on to completed tasks
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Threads in TIMED_WAITING causing build agents to hold on to completed tasks Change By: laurent gil Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached.Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out.*Jenkins Version:* 2.150.3 *Plugins:* [^jenkins-plugins.txt]*^Java version:^* ^openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode)^May be related with https: / /issues.jenkins-ci.org/browse/ JENKINS-56480Regards Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Threads in TIMED_WAITING causing build agents to hold on to completed tasks
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Threads in TIMED_WAITING causing build agents to hold on to completed tasks Change By: laurent gil Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached.Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out.*Jenkins Version:* 2.150.3 *Plugins:* [^jenkins-plugins.txt]*^Java version:^* ^openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode)^ May be related with https://issues.jenkins-ci.org/browse/JENKINS-56480 Regards Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Threads in TIMED_WAITING causing build agents to hold on to completed tasks
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Threads in TIMED_WAITING causing build agents to hold on to completed tasks Change By: laurent gil Summary: Jenkins worker not released Threads in TIMED_WAITING causing build agents to hold on to completed tasks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Jenkins worker not released
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Jenkins worker not released Change By: laurent gil Component/s: github-branch-source-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Jenkins worker not released
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Jenkins worker not released Change By: laurent gil Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached.Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out.*Jenkins Version:* 2.150.3* Dump:* [^jenkins_dump.txt]* Plugins:* [^jenkins-plugins.txt]*^Java version:^* ^openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode)^Regards Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Jenkins worker not released
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Jenkins worker not released Change By: laurent gil Attachment: jenkins_dump.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-31536) Jobs hanging in Build Executor even if it is finished
Title: Message Title laurent gil edited a comment on JENKINS-31536 Re: Jobs hanging in Build Executor even if it is finished Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached.Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out.*Jenkins Version:* 2.150.3* Dump:* [^jenkins_dump.txt]* Plugins:* [^jenkins-plugins.txt]*^Java version:^* ^openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode)^ Regards Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Jenkins worker not released
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Jenkins worker not released Change By: laurent gil Summary: Jenkins workder worker not released Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56441) Jenkins workder not released
Title: Message Title laurent gil created an issue Jenkins / JENKINS-56441 Jenkins workder not released Issue Type: Bug Assignee: Unassigned Attachments: jenkins-plugins.txt, jenkins_dump.txt Components: core Created: 2019-03-06 12:55 Priority: Critical Reporter: laurent gil Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached. Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out. Jenkins Version: 2.150.3 Dump: jenkins_dump.txt Plugins: jenkins-plugins.txt Java version: openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode) Regards Add Comment
[JIRA] (JENKINS-31536) Jobs hanging in Build Executor even if it is finished
Title: Message Title laurent gil commented on JENKINS-31536 Re: Jobs hanging in Build Executor even if it is finished Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached. Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out. Jenkins Version: 2.150.3 Dump: jenkins_dump.txt Plugins: jenkins-plugins.txt Java version: openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode) Regards Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-31536) Jobs hanging in Build Executor even if it is finished
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-31536 Jobs hanging in Build Executor even if it is finished Change By: laurent gil Attachment: jenkins-plugins.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-31536) Jobs hanging in Build Executor even if it is finished
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-31536 Jobs hanging in Build Executor even if it is finished Change By: laurent gil Attachment: jenkins_dump.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-31536) Jobs hanging in Build Executor even if it is finished
Title: Message Title laurent gil commented on JENKINS-31536 Re: Jobs hanging in Build Executor even if it is finished I have a similar issue with the version 2.167. The first occurrence was with the version 2.166. Any help will be appreciated. Thanks ! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-49753) EC2 cloud Windows nodes terminate as soon as connected
Title: Message Title laurent gil commented on JENKINS-49753 Re: EC2 cloud Windows nodes terminate as soon as connected Can you please share your configuration to access the windows slave through cygwin. In my side i installed cygwin i manage to access the windows box with ssh from a bash but the ec2 plugins seems to fail after the connection. I guess this code alway return false https://github.com/jenkinsci/ec2-plugin/blob/495adac020384e8601b0ec40a2fa52b8123d8647/src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java#L284 whereas i manage to start ubuntu box with the same ssh privatekey. Any idea ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54699) Durable Task Version 1.28 break jenkins pipeline
Title: Message Title laurent gil commented on JENKINS-54699 Re: Durable Task Version 1.28 break jenkins pipeline Devin Nusbaum, yes we rollback Durable Tasks to the version 1.27. Our script security plugin is in version 1.48. Basically we update all the plugins once a week except Durable Tasks and Docker pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54699) Durable Task Version 1.28 break jenkins pipeline
Title: Message Title laurent gil created an issue Jenkins / JENKINS-54699 Durable Task Version 1.28 break jenkins pipeline Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2018-11-19 14:47 Environment: Linux Ubuntu 16.04 x64 Jenkins 2.138.1 Priority: Critical Reporter: laurent gil When we execute workflow pipeline containing global shared lib, we receive the following exception. None of the workflow job runs whereas a freestyle job does not have any issue. [Office365connector] No webhooks to notify https://jenkins.platformdxc.com/job/Platform%20DXC/job/release-pipeline/view/change-requests/job/PR-729/4/console#L28GitHub has been notified of this commit’s build result https://jenkins.platformdxc.com/job/Platform%20DXC/job/release-pipeline/view/change-requests/job/PR-729/4/console#L30java.lang.AssertionError https://jenkins.platformdxc.com/job/Platform%20DXC/job/release-pipeline/view/change-requests/job/PR-729/4/console#L31 at com.google.common.cache.LocalCache$Segment.expireEntries(LocalCache.java:2653) https://jenkins.platformdxc.com/job/Platform%20DXC/job/release-pipeline/view/change-requests/job/PR-729/4/console#L32 at com.google.common.cache.LocalCache$Segment.tryExpireEntries(LocalCache.java:2638) https://jenkins.platformdxc.com/job/Platform%20DXC/job/release-pipeline/view/change-requests/job/PR-729/4/console#L33 at com.google.common.cache.LocalCache$Segment.getLiveValue(LocalCache.java:2774) https://jenkins.platformdxc.com/job/Platform%20DXC/job/release-pipeline/view/change-requests/job/PR-729/4/console#L34 at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2214) https://jenkins.platformdxc.com/job/Platform%20DXC/job/release-pipeline/view/change-requests/job/PR-729/4/console#L35 at
