-
Notifications
You must be signed in to change notification settings - Fork 841
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
build_log_retention.days not respected #8943
Labels
Comments
jonnydotgg
added a commit
to jonnydotgg/concourse
that referenced
this issue
Apr 10, 2024
…t globally, if not use job spec
Accidentally duplicated this with a PR 🤦 closing this one. See #8944 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
build_log_retention.days
is being ignored and defaulting to0
ifCONCOURSE_MAX_BUILD_LOGS_TO_RETAIN
is set butCONCOURSE_MAX_DAYS_TO_RETAIN_BUILD_LOGS
is not.The same applies the other way round,
build_log_retention.builds
is ignored and defaults to0
ifCONCOURSE_MAX_DAYS_TO_RETAIN_BUILD_LOGS
is set butCONCOURSE_MAX_BUILD_LOGS_TO_RETAIN
is not.Steps to reproduce
CONCOURSE_MAX_BUILD_LOGS_TO_RETAIN: 5
indocker-compose.yml
build_log_retention.builds
to 3 and setbuild_log_retention.days
to 7 (see example below).atc.reaper.tick.build-reaper.start
logExpected results
Logs should not be reaped until 7 days later.
Actual results
Logs are reaped at 0 days!
Additional context
Example pipeline for testing...
Triaging info
v7.9.1
The text was updated successfully, but these errors were encountered: