So this is the same issue as described in the now-closed issue here , but basically we have the “environment” env variable set to “test” which is a pretty reasonable thing to do, and now all of our logs have all the instances of the word “test” converted to “****”, which is quite annoying. I apprecia…

Heya @OisinMoran - we can turn off this feature per-project if you submit a support ticket :slight_smile: We are working to improve this feature with self-service opt-out.

"test" replaced with "****" in output

Feedback & Bug Reports Product Feedback

system Closed March 14, 2020, 1:53pm 3

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Config-translation does not handle ENV variables with spaces in them Feedback & Bug Reports config-translation	2	1937	June 18, 2018
Unwanted output in the test output Build Environment bash	2	1484	June 18, 2018
Setting ENV VARS is causing my build to crash loop Feedback & Bug Reports	1	699	June 18, 2018
"Persisting to Workspace" generating extremely large log output Build Environment	3	714	December 27, 2018
Enviroment dies with memory limit Build Environment	3	1047	June 18, 2018

"test" replaced with "****" in output

Related topics