|
||||||||
|
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.
What's your goal?
If it's providing your users a child-proof UI (e.g. to prevent config mistakes), check out the Cloudbees Template plugin. It only provides UI for what you explicitly allow configured. Cloudbees Nodes Plus helps as well, limiting some nodes to running jobs that are explicitly allowed to run on them, independent of the label mechanism. IOW, it can be done in plugins.
If it's security, just forget about that. You absolutely need to be able to trust the users you give job config permissions. Hiding an input field will not achieve this. I'd run multiple masters instead, to prevent untrusted users from messing with your stuff.
Or something else entirely?