|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Sorry, but I don't get yours or mwebbers point. The first page of the Google job results led me to here, opening an issue for the configuration slicing plugin as requested.
In https://issues.jenkins-ci.org/browse/JENKINS-20327 you said that this issue is not a core problem but a problem of the job configuration slicing plugin. The next suggestion of mwebber was: (16/Okt/14 3:26 PM) @marco, you should open a separate issue for the job config slicing plugin (this issue is for the core problem). Also, if you read the comments above, you will find a workaround.
And just to remeber: I do not have millions of jobs. I just have 100. Why does the configuration slicing plugin lists all the modules of a job at all? The unnecessary listing of modules causes this problem. From my point of view this issue is not fixed at all, I just have a workaroud and it would be great if you could reopen it or at least create a follow up issue.