Continuous Delivery with Docker and Jenkins

Security

The way you should approach the Jenkins security depends on the Jenkins architecture you have chosen within your organization. If you have a Jenkins master for every small team, then you may not need it at all (under the assumption that the corporate network is firewalled). However, if you have a single Jenkins master instance for the whole organization, then you'd better be sure you secured it well.

Jenkins comes with its own user database-we have already created a user during the initial configuration process. You can create, delete, and modify users by opening the Manage Users setting page. The built-in database can be a solution in case of small organizations; however, for the large group of users, you will probably want to use ...