Allow repositories to specify where `.travis.yml` should be found

config
#1

I’d like to keep repository free from CI configuration noise.

e.g. Appveyor CI allows to provide an URL to YAML config on project settings in Appveyor GUI.
It’s great also for other reason, as that way I can easily share common config among projects that require same setup.

Is there any way to achieve that with Travis CI? If not, is it somewhere on a roadmap?

Can I use a different file than .travis.yml?
Support the recommended YAML extension of `.yaml` for Travis CI project configurations
#2


and

also ask for different locations for looking for the configuration file.

1 Like
#3

I would very much like if .travis.yml could be moved to a subdirectory of our choice.

Note that this topic (which we were redirected to from github issues) seems to conflate two different requests:

  • [1] Specify local pathname to travis.yml. Depending how implemented, renaming .travis.yml to travis.yml can be the same feature. (this is my request).
  • [2] Host travis.yml externally (aka possibly set a web url instead of the local pathname), this is what OP requested (I pesonally don’t need this, but it could be seen as an extension of [1]. Arguably [1] without [2] is easier to implement).

Thank you.

3 Likes
#4

It would be nice to be able to put the file in .github/travis.yml or allow for a configurable file name in the web UI for a repository.

This would allow for reducing the number of files in the root of the repository, while allowing for easier dealing with per-project quirks related to that.

#5

This feature would be very useful for us too. As our project grows, our CI structure and pipeline grows too, and it would be nice to organize everything in a directory, such as ci/travis.yml, ci/script_foo, ci/script_bar, instead of having files scattered in multiple places. :+1:

2 Likes
#6

Any update on this feature? I would like travis CI to be triggered only if there are changes in that directory. I followed issue thread #5519 filed by ottok. Any update? or any alternatives to achieve this?