Skip to content

Commit 5c437ae

Browse files
d3xter666KlattGRandomByte
authored
[INTERNAL] Document UI5_LOG_LVL in Troubleshooting page (#850)
JIRA: CPOUI5FOUNDATION-490 --------- Co-authored-by: Günter Klatt <[email protected]> Co-authored-by: Merlin Beutlberger <[email protected]>
1 parent 164fc2b commit 5c437ae

File tree

1 file changed

+29
-0
lines changed

1 file changed

+29
-0
lines changed

docs/pages/Troubleshooting.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,3 +23,32 @@ rm -rf ~/.ui5/framework/
2323
```
2424

2525
Any missing framework dependencies will be downloaded again during the next UI5 Tooling invocation.
26+
27+
## Environment Variables
28+
### Changing the Log Level
29+
30+
In CI environments or in a combination with other tools, the usage of [UI5 CLI's `--log-level`](https://sap.github.io/ui5-tooling/stable/pages/CLI/#common-options) command parameter might be inconvenient and even impossible.
31+
32+
#### Resolution
33+
34+
Replace UI5 Tooling's `--log-level` option with the `UI5_LOG_LVL` environment variable.
35+
36+
Example:
37+
38+
`UI5_LOG_LVL=silly ui5 build`
39+
40+
On Windows:
41+
42+
`set UI5_LOG_LVL=silly ui5 build`
43+
44+
Cross Environment via [cross-env](https://www.npmjs.com/package/cross-env):
45+
46+
`cross-env UI5_LOG_LVL=silly ui5 build`
47+
48+
UI5 + Karma:
49+
50+
`cross-env UI5_LOG_LVL=verbose npm run karma`
51+
52+
53+
!!! warning
54+
The combination of the `UI5_LOG_LVL` environment variable with the `--log-level` CLI parameter might lead to unexpected results; they should be used interchangeably but not together. The CLI parameter takes precedence over the `UI5_LOG_LVL` environment variable.

0 commit comments

Comments
 (0)