[JIRA] (JENKINS-41864) Illegal dates for cron entry cause 100% cpu
Title: Message Title stefan thomasson commented on JENKINS-41864 Re: Illegal dates for cron entry cause 100% cpu Having the next-executions plugin https://wiki.jenkins-ci.org/display/JENKINS/Next+Executions installed also spawns new threads at 100% Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41864) Illegal dates for cron entry cause 100% cpu
Title: Message Title stefan thomasson created an issue Jenkins / JENKINS-41864 Illegal dates for cron entry cause 100% cpu Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Feb/08 9:36 PM Environment: Jenkins 2.45 Priority: Critical Reporter: stefan thomasson Similar to JENKINS-25897 In a freestyle project, enter a cron with an illegal date like 0 0 31 6 * When saving or moving focus out of the entry box it will create a thread at 100% cpu. A new thread will be created each time, after saving, that you try to configure this job. Tested on LTS 1.651.3 ? 2.45 Handling GET /job/xx/descriptorByName/hudson.triggers.TimerTrigger/checkSpec from 127.0.0.1 : RequestHandlerThread5 java.util.GregorianCalendar.add(Unknown Source) hudson.scheduler.CronTab$CalendarField$3.rollUp(CronTab.java:270) hudson.scheduler.CronTab.floor(CronTab.java:396) hudson.scheduler.CronTabList.previous(CronTabList.java:134) hudson.triggers.TimerTrigger$DescriptorImpl.updateValidationsForNextRun(TimerTrigger.java:106) hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(TimerTrigger.java:91) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
[JIRA] [build-flow-plugin] (JENKINS-29595) Build-flow project not sending mail notification
Title: Message Title stefan thomasson commented on JENKINS-29595 Re: Build-flow project not sending mail notification I have tested "Build other projects" and at least that is not executed unless "Flow run needs a workspace" is checked. 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] [build-flow-plugin] (JENKINS-29595) Build-flow project not sending mail notification
Title: Message Title stefan thomasson edited a comment on JENKINS-29595 Re: Build-flow project not sending mail notification I have tested "Build other projects" and at least that is not executed unless *"Flow run needs a workspace"* is checked. And this seem to be the case for all post build actions. 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] [build-flow-plugin] (JENKINS-26173) Nested buildflow ignore instructions are not working
Title: Message Title
stefan thomasson commented on JENKINS-26173
Re: Nested buildflow ignore instructions are not working
You forgot to wrap the ignore in curly braces. This works for me,
parallel( { build("job1") }
, { ignore(FAILURE) { build("IdoNotExist") }
}, { build("job2") }
)
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] [build-flow-plugin] (JENKINS-29595) Build-flow project not sending mail notification
Title: Message Title stefan thomasson commented on JENKINS-29595 Re: Build-flow project not sending mail notification Not sure, but try enabling the workspace. buildNeedsWorkspacefalse/buildNeedsWorkspace 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] [build-flow-plugin] (JENKINS-30102) The wrong build is cancelled if it is still in queue
Title: Message Title stefan thomasson commented on JENKINS-30102 Re: The wrong build is cancelled if it is still in queue Pull reques https://github.com/jenkinsci/build-flow-plugin/pull/61 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] [build-flow-plugin] (JENKINS-25952) Build flow does not release threads for scheduled or queued jobs after an abort
Title: Message Title stefan thomasson commented on JENKINS-25952 Re: Build flow does not release threads for scheduled or queued jobs after an abort Could you check if this pull request ? It could be duplicate for JENKINS-20102 https://github.com/jenkinsci/build-flow-plugin/pull/61 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] [build-flow-plugin] (JENKINS-30102) The wrong build is cancelled if it is still in queue
Title: Message Title stefan thomasson created an issue Jenkins / JENKINS-30102 The wrong build is cancelled if it is still in queue Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow-plugin Created: 23/Aug/15 3:48 PM Environment: build flow 0.18 LTS jenkins 1.595 ? Priority: Critical Reporter: stefan thomasson If I as an example have a job like this build(job1, param: param) If there is already a queue of job1 and I cancel the buildflow job, it will cancel the one at the head of the queue, not the one that the build flow put in the queue. Add Comment
