Skip to content
This repository was archived by the owner on May 10, 2018. It is now read-only.

Conversation

@drogus
Copy link
Contributor

@drogus drogus commented Nov 13, 2013

We use file configs for some apps and ENV config for the others. When
both configs are available (for example because someone accidentally set
an ENV config where file config is already set), Travis.config will
silently prefer ENV over file config.

I have tested this on staging and it raises on such situation properly.

We use file configs for some apps and ENV config for the others. When
both configs are available (for example because someone accidentally set
an ENV config where file config is already set), Travis.config will
silently prefer ENV over file config.

This commit raises an error in such situation
@roidrage
Copy link
Contributor

I'm a bit torn on this. It's a good idea to handle this situation better, but should we maybe focus on getting stuff out of config files and into environment variables?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants