Builds trigger via API with custom config suddenly stopped working

We’ve been triggering builds via the V3 API for months now. Suddenly today the builds won’t start. The API request to trigger the build seems fine, we get back response and everything looks normal. But the build never starts. Is this related to a recent maintenance?

I think it might be related to pass in a config. If I remove config from the request it seems to build. But of course I need to pass in config to customize the build. Any ideas? Did support for config get changed?

spent the whole day troubleshooting this too and finally arrived to this conclusion as well after eliminating all other factors.

the only way we’ve been able to get the V3 API to trigger builds is by NOT providing a config section ie. “config”: null

works:

curl -X POST \
  -H "Content-Type: application/json" \
  -H "Travis-API-Version: 3" \
  -H "Authorization: token YOURTOKENHERE" \
  -d '{ "request": {
        "message": "Override the commit message: this is an api request", "branch": "master" }}'\
  https://api.travis-ci.com/repo/ORGNAME%2FREPONAME/requests

fails:

curl -X POST \
  -H "Content-Type: application/json" \
  -H "Travis-API-Version: 3" \
  -H "Authorization: token YOURTOKENHERE" \
  -d '{ "request": {
        "message": "Override the commit message: this is an api request", "branch": "master", "config": { "script": "echo 123" } }}'\
  https://api.travis-ci.com/repo/ORGNAME%2FREPONAME/requests

you can also test the same thing by going into the travis gui and using the “trigger build” and try it with and without entering something in the custom config section

Imprint