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
When it fails, the majority of useful prints are at the end.
As an alternative, would it be possible to get publish the tail of the Build log?
Ideally I'd like to see the full Build log, but I don't know the reason(s) why it is currently getting truncated or what the limit is (Jenkins vs GitHub restrictions/limitations?)
The text was updated successfully, but these errors were encountered:
It's a GitHub restriction 65535 bytes or so I think. and yes the tail makes sense and should be fine to swap to using that.
May be a bit more complex, but worth doing imo
Dependencies
Feature Request
Our pipeline step prints a decent amount to the console logs:
When it fails, the majority of useful prints are at the end.
As an alternative, would it be possible to get publish the tail of the Build log?
Ideally I'd like to see the full Build log, but I don't know the reason(s) why it is currently getting truncated or what the limit is (Jenkins vs GitHub restrictions/limitations?)
The text was updated successfully, but these errors were encountered: