Never rely on the Jenkins URL to not be known outside your team or organization alone for security. Logged-in users can do anything. Using the logged-in users ...
The /whoAmI/ URL allows determining who the current user is. It is available to users without permissions to troubleshoot permissions issues. /wsagents/ handles ...
... Jenkins. As a rule of thumb, it should not be used. Never rely on the Jenkins URL to not be known outside your team or organization alone for security.
This throws an exception if the user accessing this URL doesn't have Administer permission. If the administrator configured no security mechanism, the ...
Missing: book/ | Show results with:book/
Customizing Content Security Policy. It is strongly recommended to set up the Resource Root URL instead of customizing Content-Security-Policy. Most of ...
It is defined by the Jenkins URL specified in the global configuration. --httpsListenAddress=$HTTPS_HOST. Binds Jenkins to listen for HTTPS requests on the IP ...
This contains the version number of Jenkins, like "1.404" This is also a good way to check if an URL is a Jenkins URL. ⇐ Change time zone · ⇑ Using Jenkins ...
Description: Determines the Content Security Policy header sent for static files served by Jenkins. Only affects instances that don't have a resource root URL ...
Click your name on the top right corner on every page, then click "Configure" to see your API token. (The URL $root/me/configure is a good shortcut.) You can ...
Missing: control/ | Show results with:control/
Downloading the client. The CLI client can be downloaded directly from a Jenkins controller at the URL /jnlpJars/jenkins-cli.jar , in effect ...