[JIRA] (JENKINS-33238) GitPlugin | Concurrent builds are serialized when publishing
Title: Message Title Jim Carrothers commented on JENKINS-33238 Re: GitPlugin | Concurrent builds are serialized when publishing Seems very likely, the only question is whether or not something in the code actually requires that restriction. 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] [junit-plugin] (JENKINS-34217) add option to disable historical statistics gathering for test results
Title: Message Title Jim Carrothers commented on JENKINS-34217 Re: add option to disable historical statistics gathering for test results Patch available: https://github.com/jenkinsci/junit-plugin/pull/42 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] [junit-plugin] (JENKINS-34217) add option to disable historical statistics gathering for test results
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-34217 add option to disable historical statistics gathering for test results Issue Type: Improvement Assignee: Unassigned Components: junit-plugin Created: 2016/Apr/14 12:08 AM Priority: Minor Reporter: Jim Carrothers On a Gerrit voter build, where the previous build result could be an entirely different patchset group, or even from an entirely different branch, it likely does not make sense to calculate how many builds a test has been failing for, or to display the test trend chart. I would like a per-job option to disable this work, as doing so would also increase performance for very busy voter builds which keep hundreds or thousands of build records at a time. Add Comment
[JIRA] [parameterized-trigger-plugin] (JENKINS-34009) plugin doesn't perform conversion for subtypes of StringParameterDefinition
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-34009 plugin doesn't perform conversion for subtypes of StringParameterDefinition Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/Apr/04 7:56 PM Priority: Minor Reporter: Jim Carrothers Pull request: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/94 ParameterDefinition types which extend StringParameterDefinition still need to be converted, when possible, in order to ensure correct handling of any additional logic implemented by the sub-type. The code change is simply to use a more exacting check then the instanceof keyword because any parameter types which sub-class StringParameterDefinition in order to avoid re-implemeting its behaviour are not currently converted when they could be. Add Comment
[JIRA] [core] (JENKINS-33332) add itemBlocked extension point to QueueTaskDispatcher
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-2 add itemBlocked extension point to QueueTaskDispatcher Issue Type: Improvement Assignee: Unassigned Components: core Created: 05/Mar/16 2:25 AM Priority: Minor Reporter: Jim Carrothers Some plugins may place a reservation on some internal resources as part of their implementation of .QueueTaskDispatcher.canRun() clearing a queue item as runnable. A new callack in QueueTaskDispatcher would be useful to allow a plugin to be notified whenever the Queue decides an item is blocked so that it can free such resources for other purposes in the meantime. Add Comment
[JIRA] [core] (JENKINS-33332) add itemBlocked extension point to QueueTaskDispatcher
Title: Message Title Jim Carrothers commented on JENKINS-2 Re: add itemBlocked extension point to QueueTaskDispatcher I'm submitted a patch to implement this request in https://github.com/jenkinsci/jenkins/pull/2084 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-29207) Enhancement: make recources addressable in build-flow plugin
Title: Message Title Jim Carrothers commented on JENKINS-29207 Re: Enhancement: make recources addressable in build-flow plugin At present there is no explicit support for either locking or unlocking resources in this fashion, but you can accomplish it by calling the appropriate APIs directly from the flow DSL as it is not currently sandboxed. I would not necessarily expect the lockable resources plugin to ever explicitly support this behaviour because it more focused on managing locks prior to builds even starting. Is it possible that the Exclusion Plugin is more suited to what you are trying to do? Again there is no explicit support between these two plugins, but you may be able to accomplish what you need via direct API calls and the plugin is intended to lock/unlock during the course of a build. 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-15761) BuildFlow task gets stuck
Title: Message Title Jim Carrothers commented on JENKINS-15761 Re: BuildFlow task gets stuck This sounds like an issue I'm having where it seems like the build flow script occasionally loses track of a build it has scheduled and thus will never complete. Whether this is a case of Jenkins never actually scheduling the job or the QueueTaskFuture returned by the Jenkins scheduleBuild2 call not functioning correctly, I do not know. 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-15015) Add support for the NodeLabel Parameter Plugin
Title: Message Title Jim Carrothers closed an issue as Fixed I can confirm that this functionality works. I'm using it in my own environment without issue. Jenkins / JENKINS-15015 Add support for the NodeLabel Parameter Plugin Change By: Jim Carrothers Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-16458) build flow plugin doesn't work with folders plugin
Title: Message Title Jim Carrothers commented on JENKINS-16458 Re: build flow plugin doesn't work with folders plugin I don't think this issue is valid anymore. I've been using the latest versions of the folders and build flow plugins for 6 months now without any problems. Including calling jobs both inside and outside folders with build flows both inside and outside folders. 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-25092) Build flow with ConcurrentModificationException when cancelling jobs
Title: Message Title Jim Carrothers commented on JENKINS-25092 Re: Build flow with ConcurrentModificationException when cancelling jobs I believe this issue would be solved by commit 44a99406346d73c9bdb17591 in pull request #57, but I was unaware of this pending issue when I did the work. 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] [jobconfighistory-plugin] (JENKINS-30205) metadata-plugin causes garbage change logs in config history lists
Title: Message Title Jim Carrothers updated an issue Jenkins / JENKINS-30205 metadata-plugin causes garbage change logs in config history lists Change By: Jim Carrothers As you can see from the attached screenshot, when the metadata plugin is installed at the same time as jobconfighistory, you get garbage entries on every job's config history page (the ones showing as by the anonymous user) whenever you edit the config. From the difference details, it appears that some of the metadata plugin's config is somehow being wiped out by the normal edit and the plugin is then restoring it. 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] [jobconfighistory-plugin] (JENKINS-30205) metadata-plugin causes garbage change logs in config history lists
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-30205 metadata-plugin causes garbage change logs in config history lists Issue Type: Bug Assignee: Mirko Friedenhagen Attachments: metadata problem.PNG Components: jobconfighistory-plugin, metadata-plugin Created: 29/Aug/15 12:06 AM Environment: Jenkins ver. 1.596.3 Linux Priority: Minor Reporter: Jim Carrothers As you can see from the attached screenshot, when the metadata plugin is installed at the same time as jobconfighistory, you get garbage entries on every job's config history page whenever you edit the config. From the difference details, it appears that some of the metadata plugin's config is somehow being wiped out by the normal edit and the plugin is then restoring it.
[JIRA] [build-flow-plugin] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)
Title: Message Title Jim Carrothers commented on JENKINS-13523 Re: Missing option "Add timestamps to the Console Output" (Build Environment) It seems that the timestamp is fully compatible with the Build Flow plugin, but it cannot be enabled through the UI due to Build Flow job types not having a "Build Environment" section. As a quick PoC, I tried added the timestamper wrapper config to the job's config.xml directly. After doing this the subsequent builds displayed timestamps as if it had been enabled normally. The downside is that as soon as the project's configuration is changed through the UI, the manual addition is removed 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] [gerrit-trigger-plugin] (JENKINS-29663) Forbidden File matches are not processed if the project does not also configure a File whitelist
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-29663 Forbidden File matches are not processed if the project does not also configure a File whitelist Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 27/Jul/15 10:40 PM Priority: Minor Reporter: Jim Carrothers The Forbidden File matches configuration is ignored unless the projects also configures one or more Files of "interest", even if the match is a Path=**. The problem is the isInteresting method call in the GerritProject class. The overloaded version which does not include the list of whitelisted files does not do any forbidden files processing. Add Comment
[JIRA] [email-ext-plugin] (JENKINS-29449) the "Send To" section of a trigger should not be exposed when configuring a "job watch"
Title: Message Title Jim Carrothers commented on JENKINS-29449 Re: the "Send To" section of a trigger should not be exposed when configuring a "job watch" From my point of view, this oddity almost makes the feature unusable due to the potential for extreme user confusion. 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] [email-ext-plugin] (JENKINS-29448) watching one job makes it looks the user is watching all jobs enabled for watching
Title: Message Title Jim Carrothers commented on JENKINS-29448 Re: watching one job makes it looks the user is watching all jobs enabled for watching I suspected that may be the case. I started investigating the feature as potentially useful and started poking at it. 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] [email-ext-plugin] (JENKINS-29449) the "Send To" section of a trigger should not be exposed when configuring a "job watch"
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-29449 the "Send To" section of a trigger should not be exposed when configuring a "job watch" Issue Type: Improvement Assignee: Alex Earl Attachments: email-ext-plugin-watching-irrelevent_options.PNG Components: email-ext-plugin Created: 15/Jul/15 10:44 PM Environment: Jenkins v1.596.3 Linux Email Extension Plugin v2.40.5 Priority: Minor Reporter: Jim Carrothers When configuring a job watch, the "Send To" portion of the trigger should not be displayed as its contents are not used when saving the configuration and are potentially confusing to the user. Note: I am browsing Jenkins as an admin user.
[JIRA] [email-ext-plugin] (JENKINS-29448) watching one job makes it looks the user is watching all jobs enabled for watching
Title: Message Title Jim Carrothers commented on JENKINS-29448 Re: watching one job makes it looks the user is watching all jobs enabled for watching I just noticed, when you stop watching a job, or manually empty the trigger list, the new job configuration is not flushed to disk immediately. Furthermore, the clearing of the user's trigger list, by the "Stop Watching" button also does not trigger a write to disk for the user's settings, though clearing the trigger list manually and submitting does. However, the job's configuration is still not saved to disk in this last scenario. 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] [email-ext-plugin] (JENKINS-29448) watching one job makes it looks the user is watching all jobs enabled for watching
Title: Message Title Jim Carrothers updated an issue Jenkins / JENKINS-29448 watching one job makes it looks the user is watching all jobs enabled for watching I'd rather not attach the full files due to the need to scrub the contents. I've attached the relevant sections. I believe the problem is related to the isWatching() check on line 93 of EmailExtWatchAction.java. Because triggers are not job specific, when the getTriggers returns, if there is a single watched job, the check is immediately true for all jobs. Change By: Jim Carrothers Attachment: watching all jobs problem - config excerpts.txt 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] [email-ext-plugin] (JENKINS-29448) watching one job makes it looks the user is watching all jobs enabled for watching
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-29448 watching one job makes it looks the user is watching all jobs enabled for watching Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 15/Jul/15 10:05 PM Environment: Jenkins v1.596.3 Linux Email Extension Plugin v2.40.5 Priority: Minor Reporter: Jim Carrothers Watching any single job makes it look like the user is watching all other jobs which use this plugin when they navigate to the jobs summary page. Furthermore, the trigger list is shared between all jobs that a user is watching (perhaps this is intentional). I have checked in the job config file and the user is only added to the watch list of the specific job they asked to watch. Add Comment
[JIRA] [build-flow-plugin] (JENKINS-28994) allow an optional synchronicity limit for parallel blocks
Title: Message Title Jim Carrothers edited a comment on JENKINS-28994 Re: allow an optional synchronicity limit for parallel blocks Pull request to fix this issue incoming : https://github . com/jenkinsci/build-flow-plugin/pull/57 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-28994) allow an optional synchronicity limit for parallel blocks
Title: Message Title Jim Carrothers commented on JENKINS-28994 Re: allow an optional synchronicity limit for parallel blocks Pull request to fix this issue incoming. 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-28994) allow an optional synchronicity limit for parallel blocks
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-28994 allow an optional synchronicity limit for parallel blocks Issue Type: Improvement Assignee: Jim Carrothers Components: build-flow-plugin Created: 19/Jun/15 11:49 PM Priority: Minor Reporter: Jim Carrothers It should be possible to specify a limit on the number of builds in a parallel block to be run at the same time, rather than having them all blindly launch at the same time and depending on the regular queue. Add Comment
