|
||||||||
|
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.
As a first workaround I appended the configuration name to the module name. Is the module name normally used in your use case or is it empty? I'm not sure if it is worth the effort to create a new tab or if the existing module tab can be reused here. (As the package tab is used for folders if the project does not support packages). What do you think? Is this already enough? You can grab the latest build from our CI server, see wiki link.