-
-
Notifications
You must be signed in to change notification settings - Fork 731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cake 0.38.1 is failing to write messages to TeamCity #2790
Comments
@patriksvensson is it possible that this is as a result of the changes for the ANSI support? |
@gep13 It might be if TC use the log instead of the console. I will take a look at it. |
@gep13 Yes, that seems to be the case. We will probably need to write messages like this using the console directly instead of using a logger. |
@gep13 @ilnur-nazmutdinov-spark I will create a fix for this later today. Both wife and kid are sick so I will try to fix it as soon as I get some time. |
@patriksvensson that would be great, thank you, but remember, family first. If you can keep me posted, I can work on putting out a patch release once a PR is up. |
IIRC, we used to use console, but then facing problems with tests. #766 |
@gep13 Awesome. Will keep you updated. |
* hotfix/0.38.2: (build) Updated version and release notes. GH-2790: Don't write CI service messages using log
🎉 This issue has been resolved in version v0.38.2 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
What You Are Seeing?
Cake is failing to write messages to TeamCity. Cake 0.37.0 works well.
What is Expected?
Cake should write messages to TeamCity successfully
What version of Cake are you using?
0.38.1
Are you running on a 32 or 64 bit system?
64
What environment are you running on? Windows? Linux? Mac?
Mac
Are you running on a CI Server? If so, which one?
TeamCity
How Did You Get This To Happen? (Steps to Reproduce)
Running cake script from TeamCity with Cake 0.38.1
We're using methods:
Output Log
All the calls has pretty the same output:
The text was updated successfully, but these errors were encountered: