Adding a console task to explain where options came from.

Review Request #2816 - Created Sept. 14, 2015 and submitted

Information
Garrett Malmquist
pants
gmalmquist/explicit-args
2192
ff536b2...
Reviewers
pants-reviews
benjyw, jsirois, zundel
Since pants allows options in config files that haven't been
registered, it's easy to accidentally typo an option and have
pants silently ignore your config.

It can also be tricky to know what options end up getting used when
you might have flags set via multiple config files, through env
variables, and by flags set in wrapper scripts.

This makes it easy to verify if options you set in pants.ini or
elsewhere are actually sticking/not getting overriden by something
else.

It might also be cool to plumb this information through to the
pants server UI at some point.

Added tests to tests/python/pants_test/option/test_options_integration.py and tests/python/pants_test/option/test_options.py.

CI went green here: https://travis-ci.org/gmalmquist/pants/builds/80306892
CI went green here: https://travis-ci.org/gmalmquist/pants/builds/80484138

Issues

  • 0
  • 8
  • 1
  • 9
Description From Last Updated
Garrett Malmquist
Benjy Weinberger
Eric Ayers
John Sirois
Garrett Malmquist
Eric Ayers
Eric Ayers
Benjy Weinberger
Garrett Malmquist
Review request changed

Status: Closed (submitted)

Change Summary:

In commit ce4a69c00367297706252f1429b11d25f505a2b9, thanks Eric & Benjy!

Loading...