[JIRA] [core] (JENKINS-19134) Disallow Users to set a custom workspace
Daniel Beck resolved JENKINS-19134 as Wont Fix Disallow Users to set a custom workspace Change By: Daniel Beck (05/Sep/14 9:08 AM) Status: Open Resolved Resolution: WontFix 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] [core] (JENKINS-19134) Disallow Users to set a custom workspace
Daniel Beck commented on JENKINS-19134 Disallow Users to set a custom workspace Tempted to resolve this as Won't Fix given that plugins can override the config screen. Anyone opposed? 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] [core] (JENKINS-19134) Disallow Users to set a custom workspace
Daniel Beck commented on JENKINS-19134 Disallow Users to set a custom workspace Steffen Breitbach Right, Cloudbees Template plugin is Jenkins Enterprise only. (Note that it's the same program, just a licensing plugin that other enterprise plugins depend on. So no additional config changes necessary after you hand them a bucket full of money.) 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] [core] (JENKINS-19134) Disallow Users to set a custom workspace
Steffen Breitbach commented on JENKINS-19134 Disallow Users to set a custom workspace My goal would be to provide a "child-proof UI" as you put it I reckon that the Template plugin would work with the CloudBees Jenkins only? 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] [core] (JENKINS-19134) Disallow Users to set a custom workspace
Steffen Breitbach commented on JENKINS-19134 Disallow Users to set a custom workspace I agree with you in terms of "users can do what they want anyway", so let's give the issue an other name: I'd like to have a choice about what to show to users in terms of configuration and what not. For example, I'd like to hide "Build when job nodes start" from non-admin users or allow usage of certain plugins for certain user groups only and so on... But still, I agree that this is something worth discussing and not a "hard" request. 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] [core] (JENKINS-19134) Disallow Users to set a custom workspace
Daniel Beck commented on JENKINS-19134 Disallow Users to set a custom workspace 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? 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] [core] (JENKINS-19134) Disallow Users to set a custom workspace
Daniel Beck commented on JENKINS-19134 Disallow Users to set a custom workspace I don't see how this would be helpful in any way. Users who are able to configure jobs can just as easily write a shell script that cd's to the forbidden directory and then dumps data there. Or select a node you don't want them to select for their jobs. There are countless potential issues with being able to configure jobs (and that's even assuming there were no arbitrary script execution issues in numerous plugins you may have installed!) I'd really like to close this as Won't Fix since it simply wouldn't be an effective solution. Any objections? 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.
