Credentials - BredaUniversityGames/JenkinsLib GitHub Wiki
Credential Management
Why Folder-Scoped Credentials Matter
Never store student credentials at the global level. Global credentials are visible to every job on the server. If Team A stores their Perforce ticket globally, Team B's jobs can reference it.
Always create credentials inside the team's folder:
- Navigate to the team's folder
- Click Credentials in the left sidebar
- Click (folder) > Global credentials (unrestricted)
- Click Add Credentials
This makes the credential visible only to jobs inside that folder.
Perforce Credentials
See perforce.sync() — Credential Setup for Password, Ticket, and SSL fingerprint instructions.
Git Credentials
See git.sync() — Credential Setup for HTTPS, SSH, and GitHub App credential instructions.
Service Credentials
Different stages require different credential types:
| Stage | Credential Kind | What to Store |
|---|---|---|
steam.deploy() |
Username with password | Steam username + password |
itch.deploy() |
Secret text | Butler API key |
gdrive.deploy() |
Secret file | GDrive service account JSON |
epic.deploy() |
Secret text | Epic client secret |
sentry.upload() |
Secret text | Sentry auth token |
github.release() |
Username with password | GitHub username + PAT (can reuse git.sync() credential) |
See each stage's documentation for detailed credential setup.