Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73462

CI integration requires a crumb "No valid crumb was included", crumbs are no longer supported, token doesn't work

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • subversion-plugin
    • None

      According to the docs at https://plugins.jenkins.io/subversion/, a CSRF token (crumb) is needed when submitting to the subversion CI trigger API.

      When a crumb is included you get this:

      ```
      Found invalid crumb XXX. If you are calling this URL with a script, please use the API Token instead. More information: https://www.jenkins.io/redirect/
      crumb-cannot-be-used-for-script
      ```

      Adding the same token used under the job API doesn't work.

            Unassigned Unassigned
            minfrin Graham Leggett
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: