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
SBT likes to output stuff with formatted colours, and Play 2.0, which now uses SBT (note play 2 and play 1 use completely different build frameworks, when deploying a play 2 app to cedar it is detected and built as a Scala app, not a play app) makes extensive use of this feature. This is nice, except when deploying, which is very often done from automated scripts, eg from Jenkins or some other CI server, or from other automated scripts, not directly from a console. It's often necessary to work with the logs in something that isn't a console, for example, in Jenkins you view the logs on a webpage, or you might be reading the logs in an editor. If you try to do this, what you get is output that looks something like this:
� Imagine stuff with ansi colour codes on it, because github kills it.
So in these cases it is necessary to turn the colours off. This is very simple to do, just pass the following argument to SBT:
-Dsbt.log.noformat=true
Thoughts? It sounds like a sensible default, being the output is piped through git.
The text was updated successfully, but these errors were encountered:
request received via @jroper
SBT likes to output stuff with formatted colours, and Play 2.0, which now uses SBT (note play 2 and play 1 use completely different build frameworks, when deploying a play 2 app to cedar it is detected and built as a Scala app, not a play app) makes extensive use of this feature. This is nice, except when deploying, which is very often done from automated scripts, eg from Jenkins or some other CI server, or from other automated scripts, not directly from a console. It's often necessary to work with the logs in something that isn't a console, for example, in Jenkins you view the logs on a webpage, or you might be reading the logs in an editor. If you try to do this, what you get is output that looks something like this:
� Imagine stuff with ansi colour codes on it, because github kills it.
So in these cases it is necessary to turn the colours off. This is very simple to do, just pass the following argument to SBT:
-Dsbt.log.noformat=true
Thoughts? It sounds like a sensible default, being the output is piped through git.
The text was updated successfully, but these errors were encountered: