ebu-tt-live-toolkit
ebu-tt-live-toolkit copied to clipboard
Travis error for gh-pages: build config file is required via settings, but config is empty.
Travis complains in its requests page that gh-pages push fails: "Build config file is required via settings, but config is empty."
See the entry in https://travis-ci.org/ebu/ebu-tt-live-toolkit/requests after a successful master commit.
At first sight the update is correct, though.
This is still happening even though the build appears to succeed.
I am wondering if Travis expects some config for the gh-pages branch (a travis.ml file?). Does not seem to be very important, though.
I also noticed it complaining but unsure what to do about it
Is this as simple as that there's no travis.yml file in the gh-pages branch, so Travis doesn't know what to do? It seems that we could use the instructions at https://docs.travis-ci.com/user/customizing-the-build/#Building-Specific-Branches to make Travis not build gh-pages branch by including in travis.yml
:
# blocklist
branches:
except:
- gh-pages
I've added that to the master config one and created a new .travis.yml on the gh-pages branch, but it still seems to report the same error for master builds that trigger a gh-pages push. "Build config file is required via repository settings, but config is empty."
Updates on gh-pages seem to work correctly, though, as the request result said "GitHub Pages branch not included via configuration." when I added the .travis.yml to it.
Just rename travis.yml
to .travis.yml
.
Please close this issue.
@Flavien-Pensato Thank you for your input. It is already called .travis.yml
- your proposal therefore makes no difference to this issue as far as I can tell?
Came across this issue while searching for a solution to the same problem - and then I found a fix, so I thought you may want to know :)
As it turns out, Travis at some point have updated their documentation (as linked a while ago in this thread) to cover this scenario:
# Build all branches, *including* gh-pages:
branches:
only:
- gh-pages
- /.*/
Thanks for that @pat - apologies for the delay in responding (holidays!).