- Introduction
- Use a specific brew tag prefix
- Portability of build-config.yaml between different PNC environments
- Disable color output
Introduction
TODO |
Use a specific brew tag prefix
This is done by specifying in your build-config.yaml
:
...
version: 1.0.0
group: test boo
brewTagPrefix: fb-1.0-pnc
builds:
- ...
If the brewTagPrefix
is null, the product version is not updated with
the brew tag prefix. Note that the product version has a brew tag prefix
generated automatically by default. This provides a way to override that
value.
Portability of build-config.yaml between different PNC environments
To be able to re-use the same build-config.yaml
between different PNC environments (i.e. staging/production):
- Use
systemimageid
instead ofenvironmentId
to specify your build environment. Thesystemimageid
of the environment will be the same across different PNC environments, however the ids will be different.
Disable color output
Disabling CLI color output is useful in environments where the logs are piped into a file, and the ANSI color commands show up in the file, making it hard to read.
This is done by either:
- using the
--no-color
flag - set the
NO_COLOR
environment variable with any value