Skip to content

Instantly share code, notes, and snippets.

@yvanzo
Created October 4, 2020 14:40
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save yvanzo/2d1bb03c86efc1a5199fd675ee8624ba to your computer and use it in GitHub Desktop.
Save yvanzo/2d1bb03c86efc1a5199fd675ee8624ba to your computer and use it in GitHub Desktop.
MusicBrainz webservice development workflow with search

Steps to bring changes to MB WS/2 (browse/lookup/search) when it affects search:

  1. Update and release mmd-schema (Mb metaData Schema) (including Relax NG schema + Java bindings)

  2. Update and release mb-solr (search server) (including unit tests) (do not deploy yet)

  3. Update sir (search indexer) (including unit tests, but that doesn’t use mb-solr) (manually test with new mb-solr using musicbrainz-docker)

  4. Release sir (do not deploy yet)

  5. Update musicbrainz-server with compatibility code to work with both the currently deployed mb-solr/sir and their new releases

    Features to be checked:

    • Search page
    • Search webservice
    • Entity field autocomplete

    Integration test enviroments:

    • Development testing with local musicbrainz-docker
    • Deployment testing with remote test.mb.o
  6. Deploy musicbrainz-server to beta.mb.o

  7. Release musicbrainz-server and deploy to production mb.o

  8. Stop sir from production

  9. Deploy new releases of mmd-schema and mb-solr to production search

  10. Deploy new sir to production

  11. Update and release musicbrainz-docker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment