Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gitlab-runner gitlab-runner
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,506
    • Issues 2,506
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • gitlab-runnergitlab-runner
  • Merge requests
  • !3403

Add archiver staging directory option to runner helper

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Arran Walker requested to merge 6610-artifact-staging-dir into main Apr 11, 2022
  • Overview 5
  • Commits 1
  • Pipelines 4
  • Changes 2

What does this MR do?

Adds an ARCHIVER_STAGING_DIR option to the Runner helper. For now, this is only used for Artifacts, but is generically named, as an archiver staging directory may be useful in other archiving contexts where files need to first be staged (before extraction, or upload etc.)

Why was this MR needed?

The workaround for #6610 (closed) was to override TMPDIR. This adds an option specifically for archiving, where you would expect larger files.

What's the best way to test this MR?

The shell executor with job below is a good way to test that the ARCHIVER_STAGING_DIR is being passed through, as it will fail, due to "/dev/null" being an invalid directory. This mimics the test added in Go also.

image: busybox:latest

stages:
  - upload
  - download

upload:
  stage: upload
  script:
    - echo "hi" > file
  artifacts:
    paths:
      - file

download:
  stage: download
  variables:
    ARCHIVER_STAGING_DIR: "/dev/null"
  script:
    - cat file

What are the relevant issue numbers?

Closes #6610 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 6610-artifact-staging-dir