[JIRA] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Tim-Christian Bloss edited a comment on JENKINS-18455 all modules of all maven projects are listed separately Hi, the problem seems to persist when using slicing to set JDK per maven project. When reconfiguring projects for new JDK versions, I see al modules of all projects listed. Environment: Debian 7.6 amd64 Oracle JRE7 1.7.0_60 Tomcat 7.0.54 Jenkins 1.554.3 Locale/Charset: de_DE.UTF-8 EDIT 20140829@1310 : Configuration Sclicing Plugin 1.38.3 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] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Tim-Christian Bloss reopened JENKINS-18455 all modules of all maven projects are listed separately Hi, the problem seems to persist when using slicing to set JDK per maven project. When reconfiguring projects for new JDK versions, I see al modules of all projects listed. Environment: Debian 7.6 amd64 Oracle JRE7 1.7.0_60 Tomcat 7.0.54 Jenkins 1.554.3 Locale/Charset: de_DE.UTF-8 Change By: Tim-Christian Bloss (28/Aug/14 11:09 AM) Resolution: Fixed Status: Resolved 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/d/optout.
[JIRA] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Jacob Robertson commented on JENKINS-18455 all modules of all maven projects are listed separately I've looked at this, and it looks pretty clear that the code changes made by Nicolas De Loof from CloudBees causes this. The plugin wasn't designed to handle "getAllItems", and that code change was made without enough testing. I have assigned the ticket to him. 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] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Jacob Robertson updated JENKINS-18455 all modules of all maven projects are listed separately Change By: Jacob Robertson (05/Jul/13 1:00 PM) Assignee: mdonohue Nicolas De Loof 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] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
T.-C. B. updated JENKINS-18455 all modules of all maven projects are listed separately Change By: T.-C. B. (24/Jun/13 10:14 PM) Labels: configuration lts-candidate plugin 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] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Daniel Beck commented on JENKINS-18455 all modules of all maven projects are listed separately Why is this labeled lts-candidate? It's not a core issue. FWIW it's probably a bug and should be resolved without adding an option. 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] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Tim-Christian Bloss created JENKINS-18455 all modules of all maven projects are listed separately Issue Type: Improvement Affects Versions: current Assignee: mdonohue Components: configurationslicing Created: 22/Jun/13 11:22 PM Description: From 1.36 to 1.37 something changed so we now see all modules of all our maven projects as separately configurable in configuration slicing. Due to the number of projects and the huge number of modules within each of them, configuration slicing lost much of its usability. Maybe the noted change "add support for folders" brought this change. Would be nice to have a global config switch to set configuration slicing to default to the old behaviour no longer showing every single maven module in config slicing lists when not explicitely chosen to do so. Reverting to 1.36 from 1.37 brought back the old behaviour for us so we can see again our projects without every single maven module listed besides them. Environment: Debian 7.0 amd64 , Oracle JRE 7.0u17 x64 , Tomcat 7.0.40 , Jenkins 1.509.1 , de_DE.UTF-8 Project: Jenkins Labels: configuration plugin lts-candidate Priority: Major Reporter: Tim-Christian Bloss 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.
