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

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.

---
Originally reported by minfrin, imported from: CI integration requires a crumb "No valid crumb was included", crumbs are no longer supported, token doesn't work

• status: Open
  
• priority: Minor
  
• component(s): subversion-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251212-090250
  

Raw content of original issue

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.