Skip to content

Fix misleading error during cache restoration

Romuald Atchadé requested to merge misleading-error-cache into main

What does this MR do?

Fix the misleading error cache during cache retrieval

Why was this MR needed?

To add more clarity and avoid user confusing the error message to a failed job

What's the best way to test this MR?

gitlab-ci
image: alpine:latest

build:
  stage: build
  script:
    - mkdir -p ./target
    - echo "hello" > ./target/hello.txt
    - 'for i in $(seq 1 60); do echo $(date) >> ./target/hello.txt; sleep 1; done'
    - echo "bye"

  cache:
    key: test-build-cache
    paths:
      - target/hello.txt
config.toml
concurrent = 1
check_interval = 30
log_level = "info"

[session_server]
  session_timeout = 1800

[[runners]]
  request_concurrency = 1
  url = "https://gitlab.com/"
  token = "_REDACTED_"
  helper_image = "HELPER_IMAGE_LINKED_TO_THIS_MR"
  executor = "kubernetes"
  [runners.custom_build_dir]
  [runners.cache]
    Type = "s3"
    Shared = true
    Path = "k8s-cache"
    [runners.cache.s3]
      ServerAddress = "s3.amazonaws.com"
      AccessKey = "_REDACTED_"
      SecretKey = "_REDACTED_"
      BucketName = "bucket"
      BucketLocation = "us-east-1"
      AuthenticationType = "access-key"
    [runners.cache.gcs]
    [runners.cache.azure]
  [runners.kubernetes]
    image = "alpine:latest"
    namespace_overwrite_allowed = ""
    privileged = false
    service_account_overwrite_allowed = ""
    pod_annotations_overwrite_allowed = ""
    allow_privilege_escalation = false
    [runners.kubernetes.affinity]
    [runners.kubernetes.volumes]
    [runners.kubernetes.dns_config]
  1. Compile the helper image based on this MR and update the config.toml using that image
  2. Start a job using the configurations above
  3. The log file will look like follow
Log

Log file

Screen_Shot_2022-03-04_at_2.14.08_PM

What are the relevant issue numbers?

close #6216 (closed)

Edited by Romuald Atchadé

Merge request reports

Loading