Make cleartool location configurable.
Review Request #11290 — Created Nov. 19, 2020 and submitted
In some cases, the cleartool executable may be in an unusual location,
have an alternate name, or users may want to use a wrapper script of
some sort. This change adds an optional settings key to allow people to
set the location or name of cleartool.
Ran unit tests.
Summary | ID |
---|---|
6867bead8f9e169dea8eb94b61fedb9c3d9ee529 |
Description | From | Last Updated |
---|---|---|
E501 line too long (83 > 79 characters) |
reviewbot | |
E303 too many blank lines (2) |
reviewbot | |
F811 redefinition of unused 'test_get_cleartool_custom' from line 27 |
reviewbot | |
E303 too many blank lines (2) |
reviewbot | |
Can we define a new named logger in this file? That'll provide some context. |
chipx86 | |
I'm not 100% sure that this will do the right thing if it's an absolute path. I think we just … |
chipx86 |
- Commits:
-
Summary ID e0b11a8e7645dad7e8815a8f00689da99eccd317 ff3881dea1d676871b3bb0ad54bf1c373acee6c0
- Change Summary:
-
Actually commit all files.
- Commits:
-
Summary ID ff3881dea1d676871b3bb0ad54bf1c373acee6c0 6867bead8f9e169dea8eb94b61fedb9c3d9ee529
Checks run (2 succeeded)
flake8
passed.
JSHint
passed.