Skip to content
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

Closed
jonnydotgg opened this issue Apr 10, 2024 · 1 comment
Closed

build_log_retention.days not respected #8943

jonnydotgg opened this issue Apr 10, 2024 · 1 comment
Labels

Comments

@jonnydotgg
Copy link

Summary

build_log_retention.days is being ignored and defaulting to 0 if CONCOURSE_MAX_BUILD_LOGS_TO_RETAIN is set but CONCOURSE_MAX_DAYS_TO_RETAIN_BUILD_LOGS is not.

The same applies the other way round, build_log_retention.builds is ignored and defaults to 0 if CONCOURSE_MAX_DAYS_TO_RETAIN_BUILD_LOGS is set but CONCOURSE_MAX_BUILD_LOGS_TO_RETAIN is not.

Steps to reproduce

  1. set CONCOURSE_MAX_BUILD_LOGS_TO_RETAIN: 5 in docker-compose.yml
  2. create a pipeline and set build_log_retention.builds to 3 and set build_log_retention.days to 7 (see example below).
  3. run the test jobs 10 times.
  4. wait for atc.reaper.tick.build-reaper.start log
  5. see that only 3 logs are kept, not 7 days

Expected results

Logs should not be reaped until 7 days later.

Actual results

Logs are reaped at 0 days!

Additional context

Example pipeline for testing...

---
jobs:
  - name: job
    build_log_retention:
      builds: 3
      days: 7
    public: true
    plan:
      - task: simple-task
        config:
          platform: linux
          image_resource:
            type: registry-image
            source: { repository: busybox }
          run:
            path: echo
            args: ["Hello world!"]

Triaging info

  • Concourse version: v7.9.1
  • Browser (if applicable):
  • Did this used to work?
@jonnydotgg
Copy link
Author

Accidentally duplicated this with a PR 🤦 closing this one.

See #8944

@jonnydotgg jonnydotgg closed this as not planned Won't fix, can't repro, duplicate, stale Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant