[JIRA] (JENKINS-58418) Job named foo.bar and foo_bar causes crash when saving view
Title: Message Title Timothy Bingaman updated JENKINS-58418 Thanks for the PR! Looks good, merged. Jenkins / JENKINS-58418 Job named foo.bar and foo_bar causes crash when saving view Change By: Timothy Bingaman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200545.1562743078000.7698.1562802960323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sectioned-view-plugin] (JENKINS-10612) Sectioned View plugin: List View sections positioned wrong when three sections are configured side by side
Title: Message Title Timothy Bingaman resolved as Fixed Jenkins / JENKINS-10612 Sectioned View plugin: List View sections positioned wrong when three sections are configured side by side Change By: Timothy Bingaman Status: Open 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] [sectioned-view-plugin] (JENKINS-19376) Sectioned view plugin does not display 3 column layout properly
Title: Message Title Timothy Bingaman resolved as Fixed Jenkins / JENKINS-19376 Sectioned view plugin does not display 3 column layout properly Change By: Timothy Bingaman Status: Open 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] [ivy-plugin] (JENKINS-30847) 1.25 upgrade broke several builds due to Java 8 requirement
Title: Message Title Timothy Bingaman assigned an issue to Kevin Formsma Jenkins / JENKINS-30847 1.25 upgrade broke several builds due to Java 8 requirement Change By: Timothy Bingaman Assignee: Timothy Bingaman Kevin Formsma 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] [sectioned-view-plugin] (JENKINS-30799) Job list in list view section config should be scrollable
Title: Message Title Timothy Bingaman resolved as Done Done. Will be released in version 1.20 Jenkins / JENKINS-30799 Job list in list view section config should be scrollable Change By: Timothy Bingaman Status: In Progress Resolved Resolution: Done 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] [sectioned-view-plugin] (JENKINS-30799) Job list in list view section config should be scrollable
Title: Message Title Timothy Bingaman started work on JENKINS-30799 Change By: Timothy Bingaman Status: Open In Progress 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] [sectioned-view-plugin] (JENKINS-30799) Job list in list view section config should be scrollable
Title: Message Title Timothy Bingaman created an issue Jenkins / JENKINS-30799 Job list in list view section config should be scrollable Issue Type: Improvement Assignee: Timothy Bingaman Components: sectioned-view-plugin Created: 05/Oct/15 2:34 PM Priority: Minor Reporter: Timothy Bingaman Would be nice if the job list in the list view section config was scrollable like in the standard Jenkins list view. Add Comment This message was sent by Atl
[JIRA] [sectioned-view-plugin] (JENKINS-8276) Add View Job Filters to the List View Section
Title: Message Title Timothy Bingaman resolved as Fixed Fix will be released in version 1.20 Jenkins / JENKINS-8276 Add View Job Filters to the List View Section Change By: Timothy Bingaman Status: Reopened 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] [sectioned-view-plugin] (JENKINS-22527) List view section in Sectioned View plugin is not column sortable
Title: Message Title Timothy Bingaman resolved as Fixed Done as part of JENKINS-25920 . Will be released in version 1.20 Jenkins / JENKINS-22527 List view section in Sectioned View plugin is not column sortable Change By: Timothy Bingaman Status: Open 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] [sectioned-view-plugin] (JENKINS-25920) The UI style no longer matches Jenkins UI style
Title: Message Title Timothy Bingaman resolved as Fixed Done. Will be released in version 1.20 Jenkins / JENKINS-25920 The UI style no longer matches Jenkins UI style Change By: Timothy Bingaman Status: Open 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] [core] (JENKINS-24340) AbstractProject: makeDisabled() performs operations even if supportsMakeDisabled() is false
Title: Message Title Timothy Bingaman commented on JENKINS-24340 Re: AbstractProject: makeDisabled() performs operations even if supportsMakeDisabled() is false Yep, sounds good. No tickets logged yet, if you could create them that'd be awesome. I ended up fixing our fork of the Ivy Plugin just by overriding makeDisabled in IvyModule using the method from before this change. Can confirm that that has restored the previous behaviour for us. c3c8ce3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24340) AbstractProject: makeDisabled() performs operations even if supportsMakeDisabled() is false
Title: Message Title Timothy Bingaman commented on JENKINS-24340 Re: AbstractProject: makeDisabled() performs operations even if supportsMakeDisabled() is false I believe this change caused a small issue in the Ivy Plugin and likely in the Maven Plugin as well. Both of those plugins, when configured to build modules as separate jobs, disable their child projects if they no longer exist in the source on a new build. In both cases, the child projects IvyModule and MavenModule are not user-disableable, but the code does still need to be able to disable them programatically. On Jenkins versions with this change, removing a module from source control, or renaming a module, will leave 'ghost' module projects around that Jenkins still tries to build, but which are not listed as modules in the parent project anymore. 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] [job-dsl-plugin] (JENKINS-29910) Add support for Ivy plugin
Title: Message Title Timothy Bingaman started work on JENKINS-29910 Change By: Timothy Bingaman Status: Open In Progress 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] [job-dsl-plugin] (JENKINS-29910) Add support for Ivy plugin
Title: Message Title Timothy Bingaman created an issue Jenkins / JENKINS-29910 Add support for Ivy plugin Issue Type: New Feature Assignee: Timothy Bingaman Components: job-dsl-plugin Created: 12/Aug/15 1:55 PM Priority: Minor Reporter: Timothy Bingaman Add support for https://wiki.jenkins-ci.org/display/JENKINS/Ivy+Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-19383) Bytecode compatibility transformer mistakenly corrupts org.apache.ivy.core.settings.IvySettings.triggers
Timothy Bingaman commented on JENKINS-19383 Bytecode compatibility transformer mistakenly corrupts org.apache.ivy.core.settings.IvySettings.triggers Any chance of this being backported to the LTS stream? It's currently broken on 1.509.4. Looks like the associated bytecode transformer logic was backported to 1.509.4, but this fix hasn't been backported yet. 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] [core] (JENKINS-19383) Bytecode compatibility transformer mistakenly corrupts org.apache.ivy.core.settings.IvySettings.triggers
Timothy Bingaman commented on JENKINS-19383 Bytecode compatibility transformer mistakenly corrupts org.apache.ivy.core.settings.IvySettings.triggers ah ok, sweet, no worries then. Using 1.509.3 at the moment without issues. Will jump on 1.532.1 when it arrives 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] [ivy] (JENKINS-18790) Ivy job type should support fingerprinting of consumed dependencies
Timothy Bingaman commented on JENKINS-18790 Ivy job type should support fingerprinting of consumed dependencies This was something I had planned (and very much wanted) to do, but I didn't get time, and haven't had time since then to even support this plugin really. The solution is pretty straightforward, but would take a bit of work. The basic approach is to attach an IvyListener to the build process which can then filter through all of the different IvyEvent objects fired during the build process, recording the resolve events to fingerprint all dependencies and recording the publish events for automatic archiving and fingerprinting of artifacts. The Jenkins Artifactory plugin already has a lot of this code for its integration with the Jenkins Ivy plugin, so their general approach could likely just be copied. I really am not going to have any time at all to work on this though, so I can only hope that some other dev will eventually come along and implement 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/groups/opt_out.
[JIRA] (JENKINS-15002) Parameterized trigger passes no parameters from Ivy Prioject
Timothy Bingaman commented on JENKINS-15002 Parameterized trigger passes no parameters from Ivy Prioject So what is the exact setup that is failing? You have one Ivy Project that is triggering another Ivy Project? Or an Ivy Project that is triggering a Freestyle Project? And what exactly do you have in the predefined parameters box? 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-15002) Parameterized trigger passes no parameters from Ivy Prioject
Timothy Bingaman commented on JENKINS-15002 Parameterized trigger passes no parameters from Ivy Prioject Not sure if it is related, but someone else added something to the Ivy Plugin related to parameters a while back. In the Ivy Project configuration, go to the Ivy Module Configuration section, expand the bottom-most Advanced section, and check the Use parameters from upstream builds. See if that does anything for you and let me know how it goes. 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-14478) 1.474 breaks adding a list-view to sectioned-view plugin
Timothy Bingaman commented on JENKINS-14478 1.474 breaks adding a list-view to sectioned-view plugin yes, the delete button problem is the same issue, so it should also be fixed in the next Jenkins release (v1.477) 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-14478) 1.474 breaks adding a list-view to sectioned-view plugin
Timothy Bingaman commented on JENKINS-14478 1.474 breaks adding a list-view to sectioned-view plugin If it really is related to the linked issues, then it has already been fixed, but not yet released. The associated fix is scheduled for Jenkins v1.477, but I have not verified if that fix actually fixes this particular problem. 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-14632) Hetero lists broken in Jenkins 1.455+ by introduction of resource adjuncts
Timothy Bingaman created JENKINS-14632 Hetero lists broken in Jenkins 1.455+ by introduction of resource adjuncts Issue Type: Bug Assignee: Unassigned Components: core Created: 31/Jul/12 2:23 AM Description: The use of elements inside newly-added items in a hetero list are broken. This appears to be caused by the introduction of resource adjuncts in Jenkins 1.455. The generated html of a entry changed in v1.455 to include these extra elements: "stylesheet" href="" class="code-quote">"/adjuncts/29830985/lib/form/section_.css" type="text/css"> "/adjuncts/29830985/lib/form/section_.js"type="text/_javascript_"> I believe it is the link element causing the problems because if I wrap the in an tag, then edit the DOM to remove the element, then the hetero list entry loads successfully when the advanced section is expanded. An example of this is the Sectioned View Plugin. If you add a new List View Section to a Sectioned View then the Advanced section (which contains a tag) is empty when expanded in Jenkins 1.455+. If you edit the DOM immediately after adding the List View Section (before clicking the Advanced button) to remove that extra element, then the Advanced section will work properly. Environment: Jenkins v1.455 Project: Jenkins Priority: Major Reporter: Timothy Bingaman 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-13212) "Advanced" button fails for newly created list view section
Timothy Bingaman edited a comment on JENKINS-13212 "Advanced" button fails for newly created list view section Looks like this was broken by a core change in Jenkins v1.455 by the introduction of resource adjuncts. Jenkins v1.454 appears to be fine. 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-13212) "Advanced" button fails for newly created list view section
Timothy Bingaman commented on JENKINS-13212 "Advanced" button fails for newly created list view section Looks like this was broken by a core change in Jenkins v1.455 by the introduction of script adjuncts. Jenkins v1.454 appears to be fine. 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-10025) Calling rebuildDependencyGraph() in cycle
[ https://issues.jenkins-ci.org/browse/JENKINS-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163524#comment-163524 ] Timothy Bingaman commented on JENKINS-10025: Hey guys, apologies for not responding sooner. I'm afraid my time to work on this project these days is pretty much nonexistent. Gregory Boissinot has taken over general maintenance (gboissinot). This particular issue is in the old Ivy trigger code as well, which is from before I took over the project a number of years ago. All my effort was focused on creating and maintaining the Ivy project type. I'm not sure how many people are using the trigger vs the project type, but the trigger hasn't been actively maintained for a fair while. That said, it may well be quite a simple fix to resolve this issue, but I'm afraid I'm not going to have time to look into it. -Timo > Calling rebuildDependencyGraph() in cycle > - > > Key: JENKINS-10025 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10025 > Project: Jenkins > Issue Type: Bug > Components: ivy >Reporter: vjuranek >Assignee: abayer >Priority: Blocker > > There probably possible cycle call of rebuildDependencyGraph(), > Ivy calls > Hudson.getInstance().rebuildDependencyGraph(); > which starts following cycle: > getModuleDescriptor() -> recomputeModuleDescriptor() -> setModuleDescriptor() > -> hudson.model.Hudson.rebuildDependencyGraph() > which results into StackOverflowError, for whole exception, see > http://groups.google.com/group/jenkinsci-users/browse_thread/thread/3c6b67b448c98379# -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12638) Rebuilding dependency graph slow on large numbers of Ivy Projects
[
https://issues.jenkins-ci.org/browse/JENKINS-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158549#comment-158549
]
Timothy Bingaman commented on JENKINS-12638:
The second part of that ({{O(xn)}}) can't be helped, but the first part
({{O(x^2)}}) is horribly inefficient.
Using the solution that was applied to the Maven Plugin for [JENKINS-7535] in
commit
[6a5330fd936fb949da74d738b82dcf5333282b61|https://github.com/jenkinsci/jenkins/commit/6a5330fd936fb949da74d738b82dcf5333282b61]
this first part can be reduced roughly to an {{O\(n\)}} operation, resulting
in a final order of about {{O(n + xn)}}.
> Rebuilding dependency graph slow on large numbers of Ivy Projects
> -
>
> Key: JENKINS-12638
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12638
> Project: Jenkins
> Issue Type: Bug
> Components: ivy
>Reporter: Timothy Bingaman
>Assignee: Timothy Bingaman
>
> Similar issue to [JENKINS-7535], but in the Ivy Plugin instead of the Maven
> Plugin.
> Every time a project is saved, Jenkins rebuilds the dependency graph.
> For Ivy Projects this includes building up a dependency map of all the Ivy
> modules in Jenkins and then applying the build triggers based on that
> information. Currently, this is being done in every single module resulting
> in an operation which is roughly in the order of {{O(n^2 + xn)}} where {{n}}
> is the number of Ivy modules in Jenkins and {{x}} is the average number of
> direct dependencies each module has.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12638) Rebuilding dependency graph slow on large numbers of Ivy Projects
[
https://issues.jenkins-ci.org/browse/JENKINS-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JENKINS-12638 started by Timothy Bingaman.
> Rebuilding dependency graph slow on large numbers of Ivy Projects
> -
>
> Key: JENKINS-12638
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12638
> Project: Jenkins
> Issue Type: Bug
> Components: ivy
>Reporter: Timothy Bingaman
>Assignee: Timothy Bingaman
>
> Similar issue to [JENKINS-7535], but in the Ivy Plugin instead of the Maven
> Plugin.
> Every time a project is saved, Jenkins rebuilds the dependency graph.
> For Ivy Projects this includes building up a dependency map of all the Ivy
> modules in Jenkins and then applying the build triggers based on that
> information. Currently, this is being done in every single module resulting
> in an operation which is roughly in the order of {{O(n^2 + xn)}} where {{n}}
> is the number of Ivy modules in Jenkins and {{x}} is the average number of
> direct dependencies each module has.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12638) Rebuilding dependency graph slow on large numbers of Ivy Projects
Timothy Bingaman created JENKINS-12638:
--
Summary: Rebuilding dependency graph slow on large numbers of Ivy
Projects
Key: JENKINS-12638
URL: https://issues.jenkins-ci.org/browse/JENKINS-12638
Project: Jenkins
Issue Type: Bug
Components: ivy
Reporter: Timothy Bingaman
Assignee: Timothy Bingaman
Similar issue to [JENKINS-7535], but in the Ivy Plugin instead of the Maven
Plugin.
Every time a project is saved, Jenkins rebuilds the dependency graph.
For Ivy Projects this includes building up a dependency map of all the Ivy
modules in Jenkins and then applying the build triggers based on that
information. Currently, this is being done in every single module resulting in
an operation which is roughly in the order of {{O(n^2 + xn)}} where {{n}} is
the number of Ivy modules in Jenkins and {{x}} is the average number of direct
dependencies each module has.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
