Customizing Content Security Policy. It is strongly recommended to set up the Resource Root URL instead of customizing Content-Security-Policy. Most of ...

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 ...

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 ...

The /whoAmI/ URL allows determining who the current user is. It is available to users without permissions to troubleshoot permissions issues. /wsagents/ handles ...

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 option can be configured in Manage Jenkins » System in the section Serve resource files from another domain. If the resource root URL is defined, Jenkins ...

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 ...

Navigate to the Manage Jenkins > Plugins page in the web UI. · Click on the Advanced tab. · Choose the .hpi file from your system or enter a URL to the archive ...

Determines the Content Security Policy header sent for static files served by Jenkins. Only affects instances that don't have a resource root URL set up. See ...

On the new agent node's Jenkins page, note the agent command line shown. It will be like: java \ -jar agent.jar \ -url <Jenkins URL> \ -secret <secret key> \ ...