You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
I use Serge on our Bitbucket Pipelines CI server and I noticed that Serge prints a lot of debugging information (about 478K lines) when running serge localize config.serge but there is no --debug option. Locally on my machine, with the same environment, everything works fine.
After hours of investigation, I found out that Serge probably usesCI environment variable which is predefined in Bitbucket Pipelines CI.
Currently, it can be fixed via unset CI during work with Serge.
Thanks.
The text was updated successfully, but these errors were encountered:
However, when implementing this, I didn't think about interfering about production use of Serge on a CI server where the same environment variable is set. So we need to distinguish these two use cases somehow...
Hi.
I use Serge on our Bitbucket Pipelines CI server and I noticed that Serge prints a lot of debugging information (about 478K lines) when running
serge localize config.serge
but there is no--debug
option. Locally on my machine, with the same environment, everything works fine.After hours of investigation, I found out that Serge probably uses
CI
environment variable which is predefined in Bitbucket Pipelines CI.Currently, it can be fixed via
unset CI
during work with Serge.Thanks.
The text was updated successfully, but these errors were encountered: