Where the data about which scopes a build can see stores?


When a build is running, obviously it must know which job it belongs to and other parents, but how does it work internally about the credentials scopes? what and how jenkins limits the specific build to see only the credentials scopes it should see, and how this process works? it is some internal information that the build gets from the jenkins internal? is it the way jenkins structure works? like literally a tree model of folders and each folder and parent folder hold the info about it’s scope?

I’d appreciate your help.
Thank you.

See the Jenkins credentials plugin consumer guide (for users of the credentials API)

If that’s not sufficient, then see the implementation guide.

1 Like