在 Debian 上部署的 Jenkins 中,权限管理主要通过 安全配置(Security Realm + Authorization Strategy) 来实现。下面按从入门到常用企业做法给你系统讲一下。
Jenkins’ own user databaseLDAP / GitHub / GitLabMatrix Authorization StrategyRole-Based Strategy(推荐)Jenkins’ own user databaseMatrix Authorization Strategyadmin -> 全部勾选
anonymous -> 全部取消
user1:
Overall: Read
Job: Read/Build
Role-based Authorization Strategy
路径:
Manage Jenkins → Manage and Assign Roles
admin -> 全部
developer -> Read, Job Read
viewer -> Read
project-A:
Pattern: project-a.*
Permissions: Build, Read
project-B:
Pattern: project-b.*
alice -> admin
bob -> developer + project-A
tom -> viewer
✅ 好处:
cat /etc/default/jenkins
通常是:
JENKINS_USER=jenkins
确保:
sudo chown -R jenkins:jenkins /var/lib/jenkins
如果用户能登录但构建失败:
sudo ls -l /var/lib/jenkins
sudo systemctl restart jenkins
适用于 Debian + 公司内部账号体系
配置示例(示意):
Server: ldap://ldap.company.com
root DN: dc=company,dc=com
User search base: ou=people
Group search base: ou=groups
然后:
❌ 忘记管理员权限 → 锁死 Jenkins
✅ 应急恢复:
sudo systemctl stop jenkins
sudo vim /var/lib/jenkins/config.xml
改:
<useSecurity>false</useSecurity>
sudo systemctl start jenkins
✅ 新手
✅ 企业
如果你愿意,我可以:
你现在是 单机 Jenkins 还是 公司内网用?