FYI the release 2.222 and therefore the new LTS line may start breaking tests that exercise REST API features due to the enforced CSRF protection[1]: Responses to POST requests will be 403 without a valid CSRF crumb.
Tests like that should be changed to enable authentication in Jenkins if they don't, and authenticate HTTP requests using an API token instead of a password. Doing that is the preferred approach to using REST APIs since 2.96. A short-term alternative to just make tests pass (but less relevant to how Jenkins is actually used) would be setting the system property hudson.security.csrf.GlobalCrumbIssuerConfiguration.DISABLE_CSRF_PROTECTION to true before Jenkins is started. 1: https://jenkins.io/changelog/#v2.222 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/628DF3F5-2C9C-4F66-998F-640B749FCBD7%40beckweb.net.
