[
https://issues.jenkins-ci.org/browse/JENKINS-12875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159566#comment-159566
]
Núria Aloy commented on JENKINS-12875:
--------------------------------------
In the Jenkins configuration page:
Error: Form.findMatchingInput is not a function
Source File:
http://jenkins.rightnow.com:8080/static/6dcd23a9/scripts/hudson-behavior.js
Line: 338
> "No valid crumb was included in the request" errors all around
> --------------------------------------------------------------
>
> Key: JENKINS-12875
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12875
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: CentOS release 5.5 (Final) 64b
> Reporter: Núria Aloy
> Attachments: add_build_step.png, configuration.png, console_log.png,
> console_side.png, plugins.png
>
>
> 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":
> h4. 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]
> h4. 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]
> h4. 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.
> h4. Manage Jenkins plugins
> * Cannot upgrade nor downgrade, see error shown [^plugins.png]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
