[JIRA] (JENKINS-33715) Cannot claim tests anymore
Title: Message Title Christian Bremer commented on JENKINS-33715 Re: Cannot claim tests anymore Andi B: Thanks for the reminder, I have swamped at work but will try to release it shortly. 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-34552) parameterFactories support for hudson.plugins.parameterizedtrigger.FileBuildParameterFactory
Title: Message Title Christian Bremer commented on JENKINS-34552 Re: parameterFactories support for hudson.plugins.parameterizedtrigger.FileBuildParameterFactory Thanks Daniel Spilker that explains it We are currently using javaposse.jobdsl.run on the command line to verify that the XML could be created. Is there any documentation how you test generate the XML when using part of the Automatically Generated DSL? 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-34552) parameterFactories support for hudson.plugins.parameterizedtrigger.FileBuildParameterFactory
Title: Message Title
Christian Bremer commented on JENKINS-34552
Re: parameterFactories support for hudson.plugins.parameterizedtrigger.FileBuildParameterFactory
Daniel Spilker
job('example') { steps { downstreamParameterized { trigger('other') { parameterFactories { fileBuildParameterFactory
Unknown macro: { filePattern('trigger*.txt') encoding('UTF-8') noFilesFoundAction('SKIP') }
} } } } }
This example does not work in the JobDSL playground(nor when I am trying to use it locally as well)
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] [job-dsl-plugin] (JENKINS-16360) Print DSL formatted config.xml for an existing Job
Title: Message Title Christian Bremer commented on JENKINS-16360 Re: Print DSL formatted config.xml for an existing Job Ethan Spoelstra I have not tried the solution, feel free to check it out. 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] [svn-revert-plugin] (JENKINS-15082) svn-revert-plugin: revert for failed builds, too
Title: Message Title Christian Bremer assigned an issue to Unassigned Jenkins / JENKINS-15082 svn-revert-plugin: revert for failed builds, too Change By: Christian Bremer Assignee: ChristianBremer 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Title: Message Title Christian Bremer commented on JENKINS-25867 Re: Gearman won't schedule new jobs even though there are slots available on master Odd, I see that it is updated now, I will try it out and get back to you with feedback. 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] [gearman-plugin] (JENKINS-28934) Option in Gearman plugin to put all Jobs in Jenkins queue
Title: Message Title Christian Bremer created an issue Jenkins / JENKINS-28934 Option in Gearman plugin to put all Jobs in Jenkins queue Issue Type: New Feature Assignee: Unassigned Components: gearman-plugin Created: 17/Jun/15 7:07 AM Priority: Critical Reporter: Christian Bremer Instead of Gearman holding it's internal queue of jobs to be triggered it would be great if there was an configuration option to allow Gearman to schedule all it's build in the ordinary Jenkins queue. For us this would allow: To get correct scheduling order between builds triggering between Jenkins and Zuul. Today jobs triggered by Jenkins are always triggered before jobs triggered by Zuul. See the build queue in Jenkins and be able to get statistics about overall build queue length in one place. If you are only using one Jenkins Master with Zuul the current implementation of Zuul with Gearman does not add any value.
[JIRA] [gearman-plugin] (JENKINS-28936) Gearman plugin should not decide on which node a build should be executed
Title: Message Title Christian Bremer updated an issue Jenkins / JENKINS-28936 Gearman plugin should not decide on which node a build should be executed Change By: Christian Bremer Summary: Gearmanpluginshould useJenkinsLoadBalancerwhenschedulingbuilds notdecideonwhichnodeabuildshouldbeexecuted 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Title: Message Title Christian Bremer commented on JENKINS-25867 Re: Gearman won't schedule new jobs even though there are slots available on master [3] does not seem to have been updated for the last 10 months, is it the correct link? 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] [gearman-plugin] (JENKINS-28936) Gearman plugin should not decide on which node a build should be executed
Title: Message Title Christian Bremer updated an issue Jenkins / JENKINS-28936 Gearman plugin should not decide on which node a build should be executed Change By: Christian Bremer TodaywhengearmanschedulesabuildgearmanitselfdecidesonwhichnodeabuildshouldbeexecutedinsteadofrelyingonJenkinsLoadBalancertodecidethenode.ThenodebalanceronJenkinsseemstobeexecutedbutthenodeisalreadydecidedbygearman.ThismakestheusernotbeingabletousethedefaultJenkinsLoadBalancer.AlsoifyouuseJenkinspluginsthataffectsschedulingtheydonotworkproperlysincegearmanhasalreadydecidedonwhichnode.Ihaveverifieditwhileusingtheseplugins. [ScoringLoadBalancerPlugin| https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+plugin ] [LeastLoadPlugin| https://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin ] [ThrottleConcurrentBuildsPlugin| https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin ] Examplelogswhenusing [ScoringLoadBalancerPlugin| https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+plugin ] Scoringfor... [ JobTriggeredBy*JenkinsOn*GenericLabel ] :generic-JENKINS06:62generic-JENKINS12:62generic-JENKINS15:27generic-JENKINS13:5generic-JENKINS10:5generic-JENKINS09:5generic-JENKINS14:5generic-JENKINS07:-50generic-JENKINS16:-83Scoringfor... [ JobTriggeredBy*Gearman*OnGenericLabel ] :generic-JENKINS09:5NOTE:TheselogsshowsthattheScoringLoadBalancergetsexecutedbutinsteadofevaluatingwhichnodesinthelabelgrouptochooseitonlyhastheoptiontoevaluatethenodethatgearmanhaschoosen. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You
[JIRA] [gearman-plugin] (JENKINS-28936) Gearman plugin should not decide on which node a build should be executed
Title: Message Title Christian Bremer assigned an issue to Christian Bremer Jenkins / JENKINS-28936 Gearman plugin should not decide on which node a build should be executed Change By: Christian Bremer Assignee: ChristianBremer 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] [gearman-plugin] (JENKINS-28934) Option in Gearman plugin to put all Jobs in Jenkins queue
Title: Message Title Christian Bremer updated an issue Jenkins / JENKINS-28934 Option in Gearman plugin to put all Jobs in Jenkins queue Change By: Christian Bremer InsteadofGearmanholdingit'sinternalqueueofjobstobetriggereditwouldbegreatiftherewasanconfigurationoptiontoallowGearmantoscheduleallit'sbuildintheordinaryJenkinsqueue.Forusthiswouldallow:-TogetcorrectschedulingorderbetweenbuildstriggeringbetweenJenkinsandZuul.TodayjobstriggeredbyJenkinsarealwaystriggeredbeforejobstriggeredbyZuul.-SeethebuildqueueinJenkinsandbeabletogetstatisticsaboutoverallbuildqueuelengthinoneplace.IfyouareonlyusingoneJenkinsMasterwithZuulthecurrentimplementationofZuulwithGearmandoesnotaddanyvalue. Firstaddedathttps://storyboard.openstack.org/#!/story/2000255but[~zaro]saidthatweshoulduseJIRAinsteadforgearmanissues 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] [gearman-plugin] (JENKINS-28936) Gearman plugin should use Jenkins LoadBalancer when scheduling builds
Title: Message Title Christian Bremer created an issue Jenkins / JENKINS-28936 Gearman plugin should use Jenkins LoadBalancer when scheduling builds Issue Type: New Feature Assignee: Unassigned Components: gearman-plugin Created: 17/Jun/15 7:23 AM Priority: Blocker Reporter: Christian Bremer Today when gearman schedules a build gearman itself decides on which node a build should be executed instead of relying on Jenkins LoadBalancer to decide the node. The node balancer on Jenkins seems to be executed but the node is already decided by gearman. This makes the user not being able to use the default Jenkins Load Balancer. Also if you use Jenkins plugins that affects scheduling they do not work properly since gearman has already decided on which node. I have verified it while using these plugins. https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+plugin https://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin Example logs when using https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+plugin Scoring for ... [JobTriggeredBy*JenkinsOn*GenericLabel]: generic-JENKINS06: 62 generic-JENKINS12: 62 generic-JENKINS15: 27 generic-JENKINS13: 5 generic-JENKINS10: 5 generic-JENKINS09: 5 generic-JENKINS14: 5 generic-JENKINS07: -50 generic-JENKINS16: -83 Scoring for ... [JobTriggeredBy*Gearman*OnGenericLabel]: generic-JENKINS09: 5 NOTE: These logs shows
[JIRA] [gearman-plugin] (JENKINS-28936) Gearman plugin should not decide on which node a build should be executed
Title: Message Title Christian Bremer updated an issue Jenkins / JENKINS-28936 Gearman plugin should not decide on which node a build should be executed Change By: Christian Bremer Todaywhengearmanschedulesabuildgearman itself it decidesonwhichnodeabuildshouldbeexecutedinsteadofrelyingonJenkins LoadBalancer todecidethenode.The Jenkins nodebalancer onJenkins seemstobeexecutedbutthenodeisalready decided predecided bygearman.ThismakestheusernotbeingabletousethedefaultJenkinsLoadBalancer.AlsoifyouuseJenkinspluginsthataffectsschedulingtheydonotworkproperlysincegearmanhasalreadydecidedonwhichnode.Ihaveverified itwhileusingthese thatthefollowing plugins . doesnotworkproperlywhengearmantriggerbuilds: [ScoringLoadBalancerPlugin|https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+plugin][LeastLoadPlugin|https://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin][ThrottleConcurrentBuildsPlugin|https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin]Examplelogswhenusing[ScoringLoadBalancerPlugin|https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+plugin]Scoringfor...JobTriggeredByJenkinsOnGenericLabel:generic-JENKINS06:62generic-JENKINS12:62generic-JENKINS15:27generic-JENKINS13:5generic-JENKINS10:5generic-JENKINS09:5generic-JENKINS14:5generic-JENKINS07:-50generic-JENKINS16:-83Scoringfor...JobTriggeredByGearmanOnGenericLabel:generic-JENKINS09:5NOTE:TheselogsshowsthattheScoringLoadBalancergetsexecutedbutinsteadofevaluatingwhichnodesinthelabelgrouptochooseitonlyhastheoptiontoevaluatethenodethatgearmanhaschoosen. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [gearman-plugin] (JENKINS-28936) Gearman plugin should not decide on which node a build should be executed
Title: Message Title Christian Bremer assigned an issue to Unassigned Jenkins / JENKINS-28936 Gearman plugin should not decide on which node a build should be executed Change By: Christian Bremer Assignee: ChristianBremer 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] [gearman-plugin] (JENKINS-28936) Gearman plugin should not decide on which node a build should be executed
Title: Message Title Christian Bremer updated an issue Jenkins / JENKINS-28936 Gearman plugin should not decide on which node a build should be executed Change By: Christian Bremer TodaywhengearmanschedulesabuildgearmanitselfdecidesonwhichnodeabuildshouldbeexecutedinsteadofrelyingonJenkinsLoadBalancertodecidethenode.ThenodebalanceronJenkinsseemstobeexecutedbutthenodeisalreadydecidedbygearman.ThismakestheusernotbeingabletousethedefaultJenkinsLoadBalancer.AlsoifyouuseJenkinspluginsthataffectsschedulingtheydonotworkproperlysincegearmanhasalreadydecidedonwhichnode.Ihaveverifieditwhileusingtheseplugins.[ScoringLoadBalancerPlugin|https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+plugin][LeastLoadPlugin|https://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin][ThrottleConcurrentBuildsPlugin|https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin]Examplelogswhenusing[ScoringLoadBalancerPlugin|https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+plugin]Scoringfor... JobTriggeredBy*JenkinsOn*GenericLabel JobTriggeredByJenkinsOnGenericLabel :generic-JENKINS06:62generic-JENKINS12:62generic-JENKINS15:27generic-JENKINS13:5generic-JENKINS10:5generic-JENKINS09:5generic-JENKINS14:5generic-JENKINS07:-50generic-JENKINS16:-83Scoringfor... JobTriggeredBy*Gearman*OnGenericLabel JobTriggeredByGearmanOnGenericLabel :generic-JENKINS09:5NOTE:TheselogsshowsthattheScoringLoadBalancergetsexecutedbutinsteadofevaluatingwhichnodesinthelabelgrouptochooseitonlyhastheoptiontoevaluatethenodethatgearmanhaschoosen. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Title: Message Title Christian Bremer commented on JENKINS-25867 Re: Gearman won't schedule new jobs even though there are slots available on master No we are not using OFFLINE_NODE_WHEN_COMPLETE=true in our instances. You are correct in your assumption that we use multiple executors slots on almost all nodes, although I have seen this on nodes with 1 slot as well. 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Title: Message Title Christian Bremer edited a comment on JENKINS-25867 Re: Gearman won't schedule new jobs even though there are slots available on master +1forthatdecisionAnyupdateontheissue . ? 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Title: Message Title Christian Bremer commented on JENKINS-25867 Re: Gearman won't schedule new jobs even though there are slots available on master +1 for that decision Any update on the issue. 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] [claim-plugin] (JENKINS-27091) No longer compiles (since Jenkins Core 1.561)
Title: Message Title Christian Bremer started work on JENKINS-27091 Change By: Christian Bremer Status: Open InProgress 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] [claim-plugin] (JENKINS-27091) No longer compiles (since Jenkins Core 1.561)
Title: Message Title Christian Bremer resolved as Fixed Released in 2.7 Jenkins / JENKINS-27091 No longer compiles (since Jenkins Core 1.561) Change By: Christian Bremer Status: InProgress Resolved 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, visit https://groups.google.com/d/optout.
[JIRA] [plot-plugin] (JENKINS-16320) Mouse-over in plot should show series name
Title: Message Title Christian Bremer closed an issue as Duplicate Jenkins / JENKINS-16320 Mouse-over in plot should show series name Change By: Christian Bremer Status: Open Closed Resolution: Duplicate 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] [plot-plugin] (JENKINS-21812) Display tooltips for columns when hovering over plot
Title: Message Title Christian Bremer commented on JENKINS-21812 Re: Display tooltips for columns when hovering over plot Sponsored this issue with 300$ at https://freedomsponsors.org/issue/685/display-tooltips-for-columns-when-hovering-over-plot 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] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category
Christian Bremer commented on JENKINS-12092 Allow a job to completely block a category Sean, are you working on resolving the merge conflicts to get it into the repo? 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] [claim-plugin] (JENKINS-15007) remove claim when build goes from failed to unstable
Christian Bremer resolved JENKINS-15007 as Wont Fix remove claim when build goes from failed to unstable Change By: Christian Bremer (24/Feb/15 6:36 PM) Status: Open Resolved Resolution: WontFix 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] [claim-plugin] (JENKINS-15007) remove claim when build goes from failed to unstable
Christian Bremer edited a comment on JENKINS-15007 remove claim when build goes from failed to unstable Unstable could be many other things, failing tests for example. I think the majority would like it the way that it currently is so I am closing the issue. When ones sees that you have fixed your errors you could also manually unclaim it. 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] [claim-plugin] (JENKINS-26976) Sticky Claim on failed build should persist only if build remains failed (not if it becomes unstable)
Christian Bremer resolved JENKINS-26976 as Wont Fix Sticky Claim on failed build should persist only if build remains failed (not if it becomes unstable) Change By: Christian Bremer (24/Feb/15 6:41 PM) Status: Open Resolved Resolution: WontFix 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] [claim-plugin] (JENKINS-23513) Claim plugin doesn't allow you to claim unstable builds.
Christian Bremer resolved JENKINS-23513 as Cannot Reproduce Claim plugin doesnt allow you to claim unstable builds. Change By: Christian Bremer (24/Feb/15 6:42 PM) Status: Open Resolved Resolution: CannotReproduce 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] [claim-plugin] (JENKINS-15007) remove claim when build goes from failed to unstable
Christian Bremer commented on JENKINS-15007 remove claim when build goes from failed to unstable Unstable could be many other things, failing tests for example. I think the majority would like it the way that it currently is so I am closing the issue. 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] [claim-plugin] (JENKINS-23513) Claim plugin doesn't allow you to claim unstable builds.
Christian Bremer commented on JENKINS-23513 Claim plugin doesnt allow you to claim unstable builds. Claiming should work for unstable builds as well, it must be an regression issue. Could you verify that it does not work with the latest release and post a minimal config.xml example in which claiming for unstable builds does not work. 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] [claim-plugin] (JENKINS-19820) Claim plugin serializes concurrent builds
Christian Bremer updated JENKINS-19820 Claim plugin serializes concurrent builds Change By: Christian Bremer (11/Feb/15 1:39 PM) Assignee: ChristianBremer 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] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category
Christian Bremer commented on JENKINS-12092 Allow a job to completely block a category That sounds like an good idea Seán. 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] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category
Christian Bremer commented on JENKINS-12092 Allow a job to completely block a category Hi Seán, Thanks for looking into this. What I am missing from your solution is the ability to throttle to 1 instance per-node not only on a global level. I think that it would be more dynamic if the original UI boxes could be used and that one could use 1 per node or 1 in total or any other combination of node/total that is lower than the category limit. Since we don't need it currently it's not needed but nice-to-have. 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] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Christian Bremer edited a comment on JENKINS-22185 Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label. I have solved this using a trigger job and a BuildParameterFactory as described on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin It would be nice if this could be solved by only using one single jenkins job without any downstream triggering. 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] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Christian Bremer commented on JENKINS-22185 Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label. I have solved this using a trigger job and a BuildParameterFactory as described on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin Although it would be nice if this could be solved by only using one single jenkins job without any downstream triggering. 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] [job-dsl-plugin] (JENKINS-26498) Add support for workflow plugin
Christian Bremer commented on JENKINS-26498 Add support for workflow plugin 300$ is up for grabs for adding support for workflow plugin: https://freedomsponsors.org/issue/619/add-support-for-workflow-plugin?alert=SPONSOR# 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] [job-dsl-plugin] (JENKINS-26498) Add support for workflow plugin
Christian Bremer created JENKINS-26498 Add support for workflow plugin Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 20/Jan/15 8:05 AM Description: Add DSL for the workflow plugin(https://github.com/jenkinsci/workflow-plugin) It would be really to not have to choose between using Job DSL and using workflows. Project: Jenkins Priority: Major Reporter: Christian Bremer 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] [job-dsl-plugin] (JENKINS-16360) Print DSL formatted config.xml for an existing Job
Christian Bremer commented on JENKINS-16360 Print DSL formatted config.xml for an existing Job My bad, I misunderstood the issue. +1 for adding support for this. 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] [job-dsl-plugin] (JENKINS-16360) Print DSL formatted config.xml for an existing Job
Christian Bremer commented on JENKINS-16360 Print DSL formatted config.xml for an existing Job 300$ is up for grabs for solving this issue at: https://freedomsponsors.org/issue/622/print-dsl-formatted-configxml-for-an-existing-job?alert=SPONSOR# 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] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category
Christian Bremer commented on JENKINS-12092 Allow a job to completely block a category 300$ is up for grabs for solving this issue at: https://freedomsponsors.org/issue/618/allow-a-job-to-completely-block-a-category?alert=SPONSOR# 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] [job-dsl-plugin] (JENKINS-16360) Print DSL formatted config.xml for an existing Job
Christian Bremer commented on JENKINS-16360 Print DSL formatted config.xml for an existing Job http://job-dsl.herokuapp.com/ ? We also generate all config.xml in gradle by executing javaposse.jobdsl.Run and passing in our dsl files. 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] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category
Christian Bremer commented on JENKINS-12092 Allow a job to completely block a category I think the ideal way to solve this is to have a multi-project throttle category that you assign to all your jobs. The multi-project throttle category should be able to have high limitations or no limitations at all. If you then create: jobA and jobB with the limitations 0/0 they should be able to run concurrently up to the multi-project throttle category limitations. jobC with the limitations 1 per node, jobC should only run on a node if no other job with the throttle category runs on the node. jobD with the limitations 1 in total, jobD should only run if no other jobs of this category is running. The UI to support this is already there, I have tried to set this up since I thought that it should work before I saw this issue 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] [claim-plugin] (JENKINS-19422) Claim publisher exception when trying to claim a build is aborted
Christian Bremer edited a comment on JENKINS-19422 Claim publisher exception when trying to claim a build is aborted Always or sometimes? Could you reduce the number of other plugins and post a minimal config.xml where it fails? 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] [claim-plugin] (JENKINS-19422) Claim publisher exception when trying to claim a build is aborted
Christian Bremer commented on JENKINS-19422 Claim publisher exception when trying to claim a build is aborted Always or sometimes, could you reduce the number of other plugins and post a minimal config.xml where it fails? 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] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Christian Bremer commented on JENKINS-22185 Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label. Hi Josh, Thanks for sharing your solution, I will look into it as an workaround. I still think that no manual code or parent job should be needed and that this is an bug. If I have a label "someLabel" that I have applied to nodeA, nodeB and nodeC. If I enable "Run on all nodes matching this label" with the description "The job will run on all nodes matching the label" for the label "someLabel" I expect the job to run on nodeA, nodeB and nodeC. 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] [git-plugin] (JENKINS-24935) Be able to clean workspace before retrying git fetch
Christian Bremer commented on JENKINS-24935 Be able to clean workspace before retrying git fetch 300$ is up for grabs for solving this issue at https://freedomsponsors.org/issue/614/be-able-to-clean-workspace-before-retrying-git-fetch?alert=SPONSOR 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] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Christian Bremer commented on JENKINS-22185 Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label. Any update on this issue? We are also experiencing the same problem. 200$ is up for grabs for solving this issue, see https://freedomsponsors.org/issue/609/job-with-nodelabel-parameter-plugin-does-not-build-in-parallel-on-all-nodes-which-share-a-label?alert=SPONSOR 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-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor We get ~5000 JnlpSlaveHandshake errors per hour: Dec 15, 2014 8:40:10 AM jenkins.slaves.JnlpSlaveHandshake error WARNING: TCP slave agent connection handler #150398 with /10.33.21.14:62740 is aborted: generic_AESL-JENKINS07 is already connected to this master. Rejecting this connection. We get these errors at all times, also when we can schedule on all slaves. 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-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor Other than that I see no errors in the log that occurs when it fails to schedule on a node although I might have missed it since our logs are flooded. 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-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor 200$ is up for grabs for this issue at: https://freedomsponsors.org/issue/598/will-not-start-builds-even-though-there-are-available-slots-on-executor 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-26020) Will not start builds even though there are available slots on executor
Christian Bremer created JENKINS-26020 Will not start builds even though there are available slots on executor Issue Type: Bug Assignee: Unassigned Attachments: ThreadDump - After doing disconnect and connect.log, ThreadDump - No jobs can be schedule on node.log Components: core Created: 11/Dec/14 3:45 PM Description: Sometimes our nodes won't be able to start new builds even though there are free slots available. A workaround for the slaves is to disconnect/connect the slave and it will start to schedule builds again. I have observed that when this happens for a slave the slave has fewer threads ongoing than an idle slave. Attaching thread dumps when this happens and after doing an disconnect/connect. We have seen this issue both on Windows(jlnp) slaves and linux(ssh) slaves as well as on the master node which is running linux. Environment: LTS 1.580.1 Project: Jenkins Priority: Critical Reporter: Christian Bremer 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Christian Bremer commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed 200$ is up for grabs for solving this issue at: https://freedomsponsors.org/issue/596/visual-studio-builds-started-by-jenkins-fail-with-fatal-error-c1090-because-mspdbsrvexe-gets-killed 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Christian Bremer commented on JENKINS-25867 Gearman wont schedule new jobs even though there are slots available on master 1. We already have concurrent builds enabled on all jobs. 2. We have the same issue when scheduling through the simple gearman client. I managed to schedule and start the job when moving it to another label than master but on master it will not start the job even though we have 6 executors available. The command I executed was: python gear_client.py -s localhost -p 4730 function build:~Update_Scripts --wait Thanks for the link to the simple gearman client, it was very neat to use to try things out. Please let me know if I can help in any other way. 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-24155) Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot
Christian Bremer commented on JENKINS-24155 Jenkins Slaves Go Offline In Large Quantities and Dont Reconnect Until Reboot 200$ is up for grabs for this issue on freedomsponsors.org https://freedomsponsors.org/issue/591/jenkins-slaves-go-offline-in-large-quantities-and-dont-reconnect-until-reboot 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-24272) jnlp slaves fail to reconnect when master is restarted
Christian Bremer commented on JENKINS-24272 jnlp slaves fail to reconnect when master is restarted 100$ is up for grabs for this issue on freedomsponsors.org https://freedomsponsors.org/issue/592/jnlp-slaves-fail-to-reconnect-when-master-is-restarted 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Christian Bremer edited a comment on JENKINS-25867 Gearman wont schedule new jobs even though there are slots available on master 1. We already have concurrent builds enabled on all jobs. 2. We have the same issue when scheduling through the simple gearman client. The job will start when assigning it to another label than master. The job will not start when assigning it to master label, the label has 6 free executors. The command I executed was: python gear_client.py -s localhost -p 4730 function build:~Update_Scripts --wait Thanks for the link to the simple gearman client, it was very neat to use to try things out. Please let me know if I can help in any other way. 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Christian Bremer created JENKINS-25867 Gearman wont schedule new jobs even though there are slots available on master Issue Type: Bug Assignee: Unassigned Attachments: gearman_master_threads.log, trunkated_jenkins_log.log Components: gearman-plugin Created: 02/Dec/14 1:28 PM Description: We have a setup with one Jenkins master and Zuul triggers the job through the Jenkins Gearman plugin. Sometimes no new jobs will be scheduled even though all slots are available. A workaround for the slaves is to disconnect/connect the slave and then new job would be scheduled again. For the master the only way to get jobs to be scheduled again is to restart the Jenkins service. When this happens on one node jobs would still be scheduled on other nodes. Attaching server thread log for gearman threads when no jobs are currently running and jobs are scheduled in the queue. Also attaching a trunkated jenkins.log by (grep -C 2 10.33.14.26_manager) Let me know if you need more logs or other info, I would be happy to help Environment: Jenkins 1.580.1 LTS Gearman plugin 0.1.1 Project: Jenkins Priority: Critical Reporter: Christian Bremer 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Christian Bremer commented on JENKINS-25867 Gearman wont schedule new jobs even though there are slots available on master Placed a bounty of 200$ for this issue on freedomsponsors. https://freedomsponsors.org/issue/595/gearman-wont-schedule-new-jobs-even-though-there-are-slots-available-on-master?alert=SPONSOR# 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Christian Bremer assigned JENKINS-25867 to Khai Do Gearman wont schedule new jobs even though there are slots available on master Change By: Christian Bremer (02/Dec/14 2:07 PM) Assignee: KhaiDo 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] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
Christian Åkerström resolved JENKINS-7824 as Fixed Claim plugin: Allow assigning builds/tests to other users Released in 2.4 today. Change By: Christian Åkerström (14/Oct/14 9:36 AM) Status: InProgress Resolved Resolution: Fixed 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] [claim] (JENKINS-17734) Claim Report view reports Error Status: 500
Christian Åkerström resolved JENKINS-17734 as Fixed Claim Report view reports Error Status: 500 Change By: Christian Åkerström (12/Dec/13 3:33 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed 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] [claim] (JENKINS-19820) Claim plugin serializes concurrent builds
Christian Åkerström resolved JENKINS-19820 as Wont Fix Claim plugin serializes concurrent builds This issue can't be fixed without removing the sticky functionality Change By: Christian Åkerström (18/Nov/13 12:49 PM) Status: Open Resolved Resolution: WontFix 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] [claim] (JENKINS-19820) Claim plugin serializes concurrent builds
Christian Åkerström commented on JENKINS-19820 Claim plugin serializes concurrent builds I think it is possible, although as I see it the sticky functionality is very central and something that most(if not all) users would like. A user already has the option to not use that claim plugin at all if it wants true concurrents builds. 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] [junit] (JENKINS-14089) JUnit report - Quarantine intermittent tests
Christian Åkerström commented on JENKINS-14089 JUnit report - Quarantine intermittent tests I like the idea, make a pull request when you think you are finished. 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] [claim] (JENKINS-17734) Claim Report view reports Error Status: 500
Christian Åkerström commented on JENKINS-17734 Claim Report view reports Error Status: 500 I will fix this for the next version, although I personally have very limited time for the next weeks. If someone make a pull request with a fix, I will look at it with high priority. 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] (JENKINS-16801) Claim Report don't list all jobs when Default View is set in Jenkins
Christian Åkerström resolved JENKINS-16801 as Fixed Claim Report dont list all jobs when Default View is set in Jenkins Fixed in 2.2 Change By: Christian Åkerström (27/Mar/13 7:56 AM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed 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] (JENKINS-16801) Claim Report don't list all jobs when Default View is set in Jenkins
Christian Åkerström closed JENKINS-16801 as Fixed Claim Report dont list all jobs when Default View is set in Jenkins Change By: Christian Åkerström (27/Mar/13 7:56 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/groups/opt_out.
[JIRA] (JENKINS-16801) Claim Report don't list all jobs when Default View is set in Jenkins
Christian Åkerström commented on JENKINS-16801 Claim Report dont list all jobs when Default View is set in Jenkins That it only shows the jobs for the "Default view" would also be a feature for some users. I am thinking about making it configurable which view the claim report shows it information from. For your use case you would have to configure a view that lists all jobs and choose that view as your "Claim view". Is that an acceptable solution for you? 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] (JENKINS-16801) Claim Report don't list all jobs when Default View is set in Jenkins
Christian Åkerström started work on JENKINS-16801 Claim Report dont list all jobs when Default View is set in Jenkins Change By: Christian Åkerström (15/Feb/13 7:56 AM) Status: Open InProgress 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] (JENKINS-16766) Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0
Christian Åkerström started work on JENKINS-16766 Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0 Change By: Christian Åkerström (12/Feb/13 9:31 AM) Status: Open InProgress 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] (JENKINS-16766) Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0
Christian Åkerström resolved JENKINS-16766 as Fixed Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0 Change By: Christian Åkerström (12/Feb/13 1:49 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed 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] (JENKINS-16766) Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0
Christian Åkerström closed JENKINS-16766 as Fixed Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0 Change By: Christian Åkerström (12/Feb/13 1:50 PM) 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/groups/opt_out.
[JIRA] (JENKINS-10071) Claim text is not shown in the same format as it is in claim edit box
Christian Åkerström assigned JENKINS-10071 to Christian Åkerström Claim text is not shown in the same format as it is in claim edit box Change By: Christian Åkerström (11/Feb/13 9:12 AM) Assignee: ChristianÅkerström 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] (JENKINS-10071) Claim text is not shown in the same format as it is in claim edit box
Christian Åkerström resolved JENKINS-10071 as Fixed Claim text is not shown in the same format as it is in claim edit box Change By: Christian Åkerström (11/Feb/13 9:14 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed 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] (JENKINS-10071) Claim text is not shown in the same format as it is in claim edit box
Christian Åkerström commented on JENKINS-10071 Claim text is not shown in the same format as it is in claim edit box Fixed in 2.0. To get the linebreak you should type somethingbr something else 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] (JENKINS-10071) Claim text is not shown in the same format as it is in claim edit box
Christian Åkerström closed JENKINS-10071 as Fixed Claim text is not shown in the same format as it is in claim edit box Change By: Christian Åkerström (11/Feb/13 9:14 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/groups/opt_out.
[JIRA] (JENKINS-12437) Sticky Checkbox to Claim Failed Builds Following the Current One
Christian Åkerström assigned JENKINS-12437 to Christian Åkerström Sticky Checkbox to Claim Failed Builds Following the Current One Change By: Christian Åkerström (11/Feb/13 9:15 AM) Assignee: ChristianÅkerström 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] (JENKINS-3534) Claim link on all views, but only works from All view
Christian Åkerström commented on JENKINS-3534 Claim link on all views, but only works from All view Fixed in 2.0 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] (JENKINS-3534) Claim link on all views, but only works from All view
Christian Åkerström resolved JENKINS-3534 as Fixed Claim link on all views, but only works from All view Change By: Christian Åkerström (11/Feb/13 9:17 AM) Status: Reopened Resolved Fix Version/s: current Resolution: Fixed 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] (JENKINS-3534) Claim link on all views, but only works from All view
Christian Åkerström closed JENKINS-3534 as Fixed Claim link on all views, but only works from All view Change By: Christian Åkerström (11/Feb/13 9:17 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/groups/opt_out.
[JIRA] (JENKINS-4169) Add ability to claim failures from the dashboard
Christian Åkerström assigned JENKINS-4169 to Christian Åkerström Add ability to claim failures from the dashboard Change By: Christian Åkerström (11/Feb/13 9:24 AM) Assignee: ChristianÅkerström 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] (JENKINS-4389) Make claim info available as regular view column
Christian Åkerström resolved JENKINS-4389 as Fixed Make claim info available as regular view column Change By: Christian Åkerström (11/Feb/13 9:27 AM) Status: Open Resolved Resolution: Fixed 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] (JENKINS-4389) Make claim info available as regular view column
Christian Åkerström closed JENKINS-4389 as Fixed Make claim info available as regular view column Change By: Christian Åkerström (11/Feb/13 9:27 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/groups/opt_out.
[JIRA] (JENKINS-4389) Make claim info available as regular view column
Christian Åkerström closed JENKINS-4389 as Fixed Make claim info available as regular view column Change By: Christian Åkerström (11/Feb/13 9:28 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/groups/opt_out.
[JIRA] (JENKINS-4389) Make claim info available as regular view column
Christian Åkerström resolved JENKINS-4389 as Fixed Make claim info available as regular view column Change By: Christian Åkerström (11/Feb/13 9:28 AM) Status: Reopened Resolved Fix Version/s: current Resolution: Fixed 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] (JENKINS-4389) Make claim info available as regular view column
Christian Åkerström reopened JENKINS-4389 Make claim info available as regular view column Change By: Christian Åkerström (11/Feb/13 9:27 AM) Resolution: Fixed Status: Closed Reopened 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] (JENKINS-5113) NullPointerException when a build is claimed or unclaimed
Christian Åkerström resolved JENKINS-5113 as Cannot Reproduce NullPointerException when a build is claimed or unclaimed Change By: Christian Åkerström (11/Feb/13 9:29 AM) Status: Open Resolved Resolution: CannotReproduce 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] (JENKINS-5113) NullPointerException when a build is claimed or unclaimed
Christian Åkerström closed JENKINS-5113 as Cannot Reproduce NullPointerException when a build is claimed or unclaimed Change By: Christian Åkerström (11/Feb/13 9:29 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/groups/opt_out.
[JIRA] (JENKINS-4377) Provide plugin description
Christian Åkerström resolved JENKINS-4377 as Fixed Provide plugin description Change By: Christian Åkerström (11/Feb/13 9:30 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed 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] (JENKINS-4377) Provide plugin description
Christian Åkerström closed JENKINS-4377 as Fixed Provide plugin description Change By: Christian Åkerström (11/Feb/13 9:30 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/groups/opt_out.
[JIRA] (JENKINS-16671) Multiple Selective Claiming of Broken Builds
Christian Åkerström updated JENKINS-16671 Multiple Selective Claiming of Broken Builds Change By: Christian Åkerström (11/Feb/13 9:31 AM) Assignee: ChristianÅkerström 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] (JENKINS-14585) Test Failure Claim Link not present for Maven test results
Christian Åkerström resolved JENKINS-14585 as Cannot Reproduce Test Failure Claim Link not present for Maven test results Change By: Christian Åkerström (11/Feb/13 9:32 AM) Status: Open Resolved Resolution: CannotReproduce 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] (JENKINS-14585) Test Failure Claim Link not present for Maven test results
Christian Åkerström closed JENKINS-14585 as Cannot Reproduce Test Failure Claim Link not present for Maven test results Change By: Christian Åkerström (11/Feb/13 9:33 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/groups/opt_out.
[JIRA] (JENKINS-15082) svn-revert-plugin: revert for failed builds, too
Christian Åkerström commented on JENKINS-15082 svn-revert-plugin: revert for failed builds, too The reason that it only reverts for unstable builds is that a failed build could be caused by some environmental problem aswell. For example: if the build fails because the build machine is out of disc space you don't want the commit to be reverted. We choosed an approach where we rather reverts less and be sure that the things that are reverted actually contain errors. Does this make sense or do you still wan't an option to revert for failed builds? 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
[JIRA] (JENKINS-15083) svn-revert-plugin: make dependency to claim plugin optional
Christian Åkerström commented on JENKINS-15083 svn-revert-plugin: make dependency to claim plugin optional We will add this to the next release 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
[JIRA] (JENKINS-15083) svn-revert-plugin: make dependency to claim plugin optional
Christian Åkerström started work on JENKINS-15083 svn-revert-plugin: make dependency to claim plugin optional Change By: Christian Åkerström (10/Sep/12 7:45 AM) Status: Open InProgress 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
