feat: update log artifact to use .gz extension when compressed #270
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dexyk
force-pushed
the
dk/push_gz_log_file
branch
from
2c3b7b3 to
8f142fb
Compare
dexyk
force-pushed
the
dk/push_gz_log_file
branch
from
8f142fb to
6e5da91
Compare
dexyk
changed the title
DamjanBecirovic
approved these changes
Feb 3, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When job logs are compressed, we now push the artifact with a
.gzsuffix (e.g.,job_logs.txt.gz) so the stored artifact name matches the file format, avoiding mismatches when pulling and verifying compressed logs.This is a breaking change for the frontend log artifact detection, the frontend must be updated to recognize
.gzlog artifacts.