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
  • #8184

Closed
Open
Created Oct 27, 2014 by Administrator@rootOwner

Fix service migration(s)

Created by: dblessing

Migration https://github.com/gitlabhq/gitlabhq/blob/master/db/migrate/20140907220153_serialize_service_properties.rb causes problems if a user upgrades directly from pre-7.3 to 7.4. The ultimate reason is that code was changed in Slack service as part of https://github.com/gitlabhq/gitlabhq/commit/20179772140ff0bdc2d61852c0a4f48ee6e4a2d0. When this code change is pulled in prior to the above mentioned migration, the webhook property is not present, which causes validation to fail.

One option is that we could opt to not run validations on the migration.

Assignee
Assign to
Time tracking