Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • M metadata-backup
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Paul Ganssle
  • metadata-backup
  • Issues
  • #1
Closed
Open
Created Dec 21, 2019 by Paul Ganssle@pganssleOwner

Find a way to adjust the tests to account for permissions-setting issues

When trying to add the CI pipeline, I am getting erroneous failures, presumably because whatever container the CI is running in won't let the code permanently alter the permissions on some files and folders see this pipeline. I have seen something similar to this with Rust playground as well.

Ideally, these tests would not require anything special to be done in order to run. If there's no way around it, we should:

  1. set up that special thing for the gitlab CI
  2. detect whether we're in an environment that supports running these kinds of tests and make the tests optional, so people don't get annoying local failures because their environment doesn't work as expected.
Assignee
Assign to
Time tracking