New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for specifying Jenkins' initial security settings #2
Comments
Depends on what you're trying to do. The basic design of this module is to get a basic jenkins instance installed. There are plenty of ways to lock this down, but the module doesn't do any of those. However, you could build a config, and distribute that to each new jenkins server as they are deployed. I actually do that with a separate module, to do puppet code testing. I really end up building on this module, to achieve the needed result. (Unfortunatly, it's hard to design a system that would work for everyone, since people's configs are so very different from each other. |
https://github.com/matthewbarr/puppet-ci , or it's in the puppet forge as well. |
Fix java dependency in metapackage :(
Merge pull request voxpupuli#2 from mbarr-snap/master
Is there anything additional we can do with this? Configuring jenkins itself I believe is currently outside the scope of this module and other than iptables (which is already implemented) I'm not sure what else to do. |
If you're just waiting on me, @matthewbarr answered my question so this is "resolved" as far as I'm concerned. Feel free to keep it open if @alberto56 and other users have been asking for something similar, and it's something you're interested in supporting. |
I understand the logic behind your answer and I closed my related issue: all security settings should be done on each server and not via puppet. |
Thanks for the responses. Sounds like this one is resolved to the limit it can be. I'm going to close it. If it needs to be re-opened, let me know. |
Plugin cleanup hsmaster
v1.1.2-release
- Update configs with modulesync_config defaults. - Add .sync.yml for additional configuration - Cleanup rubocop and puppet-lint failures in code - Improve some unit tests
Is there a way to secure the jenkins server or generally customize the initial configuration?
The text was updated successfully, but these errors were encountered: