Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.admin bob.admin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.adminbob.admin
  • Issues
  • #107
Closed
Open
Issue created Dec 14, 2018 by André Anjos@andre.anjos💬Owner

Absolute paths for artifacts and cache don't work in shell runners

As it turns out, we are using absolute paths to declare to-be cached files and artefacts, typically based on the settings for ${CONDA_ROOT}, which is in turn located inside ${CI_PROJECT_DIR}.

While this path is well situated inside the project build directory, the behaviour of the runners differ with respect to the fact the path is absolute:

  1. Both docker-based and macos (shell) runners understand that the path is located within the project directory and can find the files to be cached or transported to dependent stages of the build
  2. The Linux shell runner does not like the fact the path is set in absolute terms and refuses to cache or zip artefacts from the builds.
Assignee
Assign to
Time tracking