Skip to content

Add Troubleshooting Case

Charl Marais requested to merge add-runner-troubleshooting-case into main

What does this MR do?

Adds a troubleshooting case to the runner troubleshooting document

Why was this MR needed?

To prevent other customers from running into this sort of issue in future,

What's the best way to test this MR?

To verify the finding you can create a new project with this pipeline.

build_failure:
  stage: test
  script:
    - date --set="2 OCT 2006 18:00:00"
    - echo "generate Artifacts" > test.txt
  artifacts:
    paths:
    - test.txt

build_succeeds:
  stage: test
  script:
    - date --set="2 OCT 2006 18:00:00"
    - echo "generate Artifacts" > test.txt
    - date --set="8 JUL 2023 01:06:00" <-- change to todays date/time
  artifacts:
    paths:
    - test.txt

There is also an existing project which demonstrate a failure job and fixed succeeding job

What are the relevant issue numbers?

ZD Ticket: https://gitlab.zendesk.com/agent/tickets/380265 Demonstrated on SaaS runners 15.9. was does not seem to affect older runners as outlined in the ticket.

Merge request reports