-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Feature] Including build failure log in main output #3349
Comments
How was this problem fixed? It's still a thing today (I can't find any option to configure where the logs are placed, at least that would allow us to upload it as an artifact for later inspection, but the current randomised path makes it almost impossible). |
In CI environments, the |
It's never worked in Google Cloud Build. We have to pass |
Looks like that will be fixed in the next release via #6377 Anyway, you can force CI to be detected by setting environment variable Also, this popped into my notifications earlier (that's why I commented in the first place) but nothing happened to trigger that notification? Strange |
@clemyan That's really great to know, we will try that. Thank you. 👍 |
We're building native deps on GitHub Actions. When build failures occur, yarn saves the log to a build.log file in a random location. Only way for us to see the log is to upload
C:\Users\RUNNER~1\AppData\Local\Temp\xfs-*\build.log
as CI artifacts.Is it possible to include build.log in the main log (process.stdout) instead of saving to a new file?
Edit: overlooked the logs at the top
The text was updated successfully, but these errors were encountered: