kochetkov-ma / allure-server

Allure Server. Save/ generate / provide allure2 reports in one place
http://allure.iopump.ru
Apache License 2.0
213 stars 63 forks source link

Declared environment variable ALLURE_CLEAN_AGEDAYS, not getting considered for cleanup. #62

Closed sunaynat closed 1 year ago

sunaynat commented 1 year ago

Environment variables have been set as below.

image

Still when I start the server on my local, I am getting below message during startup and my config, doesn't get picked up. Am i doing something wrong here?

image
kochetkov-ma commented 1 year ago

was an issue in https://github.com/kochetkov-ma/allure-server/releases/tag/v2.11.3

what version do you use? use latest https://github.com/kochetkov-ma/allure-server/releases/tag/v2.11.4 and attach the logs with prefix [ALLURE SERVER CONFIGURATION]

sunaynat commented 1 year ago

Using https://hub.docker.com/r/kochetkovma/allure-server latest docker image.

image

echo $ALLURE_CLEAN_AGEDAYS gives 120

kochetkov-ma commented 1 year ago

I passed this variables to container:

  ALLURE_CLEAN_AGE_DAYS: 7
  ALLURE_CLEAN_PATHS_0_PATH: "main/create-report:e2e"
  ALLURE_CLEAN_PATHS_0_AGE_DAYS: 90
  ALLURE_CLEAN_PATHS_1_PATH: "master/create-report:e2e"
  ALLURE_CLEAN_PATHS_1_AGE_DAYS: 90

And I have this configuration in log

CleanUp policy settings:
{
  "dryRun" : false,
  "time" : "00:00:00",
  "ageDays" : 7,
  "paths" : [ {
    "path" : "main/create-report:e2e",
    "ageDays" : 90,
    "edgeDate" : "2023-03-24T13:11:57.347935"
  }, {
    "path" : "master/create-report:e2e",
    "ageDays" : 90,
    "edgeDate" : "2023-03-24T13:11:57.348381"
  } ],
  "minAge" : 7,
  "closestEdgeDate" : "2023-06-15T13:11:57.348457",
  "edgeDate" : "2023-06-15T13:11:57.348503",
  "notDryRun" : true
}

If your variables dont work it means they were passed to container incorrect. Check you variables in container shell by comman like echo $ALLURE_CLEAN_AGE_DAYS. It is not allure server's problem at all