Feature request: override config file settings

[rlipscombe]

With code coverage enabled, the build times are greatly increased. Currently, the only way (that I know of) to enable/disable code coverage on demand is to have an alternative configuration file, which then needs to be kept in sync with the original.

I'd like some way to be able to override certain config file settings. Potentially via environment variables, extra command line arguments, or by specifying more than one configuration file.

[ferd]

Wouldn't using a test profile for compiler options solve these issues?

[rlipscombe]

I don't know. What's a "test profile"?

In this particular case, I'm talking about rebar eunit. With code coverage enabled, the tests take ~210 seconds; with code coverage disabled, they take ~90 seconds. We use a lot of meck, though, which means recompilation while the test is running, which probably inflates the impact of coverage.

[ferd]

Profiles are still changing, but here's there temporary specification: https://gist.github.com/tsloughter/1e16d70268182db1415a

[rlipscombe]

Thanks. Yes, that looks like it might fit. Note that I'm not necessarily talking about compiler options so much as the cover_enabled and cover_print_enabled flags, but same thing, I guess.

[tsloughter]

@rlipscombe profiles work for any config option. It should be what you want http://www.rebar3.org/v1.0/docs/profiles

[tsloughter]

Closing. This is covered by http://www.rebar3.org/v1.0/docs/profiles and http://www.rebar3.org/v3.0/docs/configuration#overrides