Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.db.base bob.db.base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.db.basebob.db.base
  • Issues
  • #18
Closed
Open
Issue created Sep 09, 2017 by Tiago de Freitas Pereira@tiago.pereiraOwner

if (Stable releases dbs <> master branches dbs): raise nightlies exception

I think some of you noticed that already; I'm just writing that to keep it registered (honestly, I don't know if we need that level control).

Currently, the place where the sqlite files are stored are the same no matter we are in a release or in the master branch. The effect of that is, when we are updating something related with protocols in the master branch, our nightlies (that tests the released packages) fails (https://gitlab.idiap.ch/bob/bob.nightlies/-/jobs/87786).

What should be the best course of action? 1 - Release a new version of the db package as soon as we have a protocol update? 2 - Create different directories for the stable and development (and we control this via bob_db_manage?

One thing that I don't understand (that may solve the issue). Why the db.sql3 is not part of the wheels?? This would solve this issue.

Assignee
Assign to
Time tracking