Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • vidjil vidjil
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,738
    • Issues 1,738
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 104
    • Merge requests 104
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • vidjilvidjil
  • vidjilvidjil
  • Issues
  • #4220
Closed
Open
Issue created Mar 12, 2020 by Mikaël Salson@mikael-sOwner

Les tests unitaires serveur peuvent échouer avec un nom de branche trop long

Voir le job #576670 (pour !618 (merged)).

Le problème vient de l'utilisation de $CI_BUILD_REF_SLUG pour la création d'un environnement virtuel Python. À la place, mettre le numéro de commit (CI_COMMIT_SHORT_SHA) ?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking