Output files for release to a new named directory #211
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
We previously moved the log files to their own directory in preparation for automating release requests. However, when an output file's location changes, the outputs from old jobs aren't removed in Airlock, so the automated release will still pick them up (and worse - they'll be the log files from a previous job, not the one that the new output files were created by. This moves the files for release to a new dedicated folder so the automated release request will pick up only these files.
rebkwok
force-pushed
the
release-output-dir
branch
from
1326dcd to
4ba3938
Compare
evansd
approved these changes
Jan 9, 2026
Contributor
evansd
left a comment
evansd
left a comment
There was a problem hiding this comment.
Ughh, this isn't great behaviour from our systems, is it? Though it's hard to know exactly which bit should behave differently.
Contributor
Author
|
Yeah, it's kind of the same thing that's come up before (outputs that a project.yaml no longer generates don't get removed) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We previously moved the log files to their own directory in preparation for automating release requests. However, when an output file's location changes, the outputs from old jobs aren't removed in Airlock, so the automated release will still pick them up (and worse - they'll be the log
files from a previous job, not the one that the new output files were created by. This moves the files for release to a new dedicated folder so the automated release request will pick up only these files.