Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5756

Closed
Open
Created Dec 04, 2013 by Administrator@rootOwner

Running 'rake gitlab:test' may wipe development database on v5.4.2.

Created by: bladealslayer

In b40ff1e0 'db:setup' was added to the gitlab:test task. Documentation still tells to run all tests with:

bundle exec rake gitlab:test

This results in db:setup being called in the default development environment, which seems to wipe all tables.

Either documentation should be updated or b40ff1e0 reverted. As developers might already be used to running bundle exec rake gitlab:test without specifying environment, probably the second option is better.

Assignee
Assign to
Time tracking