Jenkins: ERROR: Could not find credentials entry with ID 'github-token'
The Jenkinsfile references a credentials ID that does not exist in the scope Jenkins can see for this job.
Could not find credentials entry with IDERROR: Could not find credentials entry with IDCredentials not found withCredentials Jenkins Meaning
Credentials live in a store and scope (system, global, folder). A job inside a folder can use global credentials and its folder's own, not a sibling folder's. IDs are case-sensitive and must match exactly; type matters too (secret text vs username/password).
Common causes
- ID misspelled or never created
- Credentials stored in a folder/store not visible to this job
- Wrong credential type for the binding
- Credentials deleted or renamed
- Multibranch scan using a different folder scope
⚡ Quick fix
- Compare the ID in Manage Jenkins → Credentials
- Create it in a scope visible to the job (global or the job's folder)
- Match the type used by
withCredentials
Detailed fix by platform
Jenkins
withCredentials([string(credentialsId: 'github-token', variable: 'TOKEN')]) { sh 'curl -H "Authorization: Bearer $TOKEN" ...' }
Code examples
Use credentials safely
withCredentials([usernamePassword(credentialsId: 'registry', usernameVariable: 'U', passwordVariable: 'P')]) {
sh 'echo "$P" | docker login -u "$U" --password-stdin registry.example.com'
}How to diagnose
- ID — Exact credentialsId?
- Scope — Visible to this job?
- Type — Matches the binding?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Cannot perform an interactive login from a non TTY device GitHub Actions: Error: Cannot perform an interactive login from a non TTY device
- Input required and not supplied GitHub Actions: Error: Input required and not supplied: token
- No such DSL method Jenkins: java.lang.NoSuchMethodError: No such DSL method 'dockerBuild' found among steps
Most viewed in CI/CD
- The process '/usr/bin/git' failed with exit code 128 GitHub Actions: Error: The process '/usr/bin/git' failed with exit code 128
- This job is stuck because you don't have any active runners GitLab CI: This job is stuck because you don't have any active runners online or available with any of these tags assigned to them
- Resource not accessible by integration GitHub Actions: Error: Resource not accessible by integration (403)
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 25 Oct 2026