-
Bug
-
Resolution: Fixed
-
Critical
-
CentOS release 5.5 (Final) 64b
After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) several parts of Jenkins have become unusable with error "No valid crumb was included in the request":
Console output
- When building, the log is unavailable, see console_log.png
- Once the build is done, the complete log is available, but the same error appears on the side console_side.png
Build configuration
- Builds cannot be launched anymore from the build page (The firebug error console displays the "No valid crumb was included in the request" error). They still can be launched from the dashboard though.
- Cannot add build steps (when choosing a build step type an error is reported in background), see add_build_step.png
Manage Jenkins configuration
- The page loads only partially (first half is permanently greyed out, see configuration.png). The firebug error console displays the "No valid crumb was included in the request" error.
Manage Jenkins plugins
- Cannot upgrade nor downgrade, see error shown plugins.png
- is duplicated by
-
JENKINS-24249 Dynamic pop-up menus don't appear when "Prevent Cross Site Request Forgery exploits" is enabled
- Resolved
-
JENKINS-27972 Credentials Scope dropdown is empty for new entry
- Resolved
-
JENKINS-25116 Jenkins won't schedule builds
- Resolved
-
JENKINS-23793 Default crumb name forbidden by nginx, breaking UI
- Closed
- is related to
-
JENKINS-14501 Enable Job link fails with "No valid crumb was included in the request"
- Resolved
-
JENKINS-7518 CLONE -Crumb breaks ajax request behind proxies. -- Still broken behind nginx proxies
- Resolved
-
JENKINS-12787 LOADING overlay does not go away on the Configure System page
- Resolved
- links to