Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl-io
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • ensembl-io
  • Merge requests
  • !87

Merged
Created Jun 18, 2019 by Marek Szuba@mks

Patch the variation test database to version 98 [release/98]

  • Overview 0
  • Commits 1
  • Changes 4

Created by: mkszuba

I forgot that patch_test_databases can only handle single-version bumps so with the test databases having only fully been sinced with 97 on the relevant release branch, the variation schema ended up remaining at 96 on master even when all other DBs got bumped to 98. Manually apply variation schema patches to bring that test DB up to date.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: rel98_variation_testdb