Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Which mode to use? #33

Open
carl-berg opened this issue Aug 26, 2019 · 1 comment
Open

Which mode to use? #33

carl-berg opened this issue Aug 26, 2019 · 1 comment

Comments

@carl-berg
Copy link
Collaborator

carl-berg commented Aug 26, 2019

Adding this question so that we can continue this discussion. In my current project i have have a few migrations (with semver2 custom versioning, which may or may not be needed). During development i started with:

  1. vNext/TableA.sql, vNext/TableB.sql
  2. Moved both files to Migrations/1.0.0
  3. Released a version into a test environment where mode = LiveField, Set mode = Brownfield locally
  4. Later on found some mistakes, added vNext/NewColumnOnTableA.sql, vNext/NewIndexOnTableB.sql
  5. Moved both scripts into Migrations/1.0.0 and made a new Release → 💣 Wouldn't allow this neither in brownfield or livefield.

I instead created a custom versioning like so:

  • Migrations/1.0.0-rc.1
  • Migrations/1.0.0-rc.3
  • Migrations/1.0.0-rc.7 (used to be vNext before release)

The problem is that i'm note quite sure if i'm using the right mode. Technically i would have liked to introduce the scripts (rc.3 and rc.7) as patch versions, however GWM doesn't recognize patch versions out of the box. Maybe i'm thinking about this wrong?

@mattiasnordqvist
Copy link
Owner

Will think more about this later, but maybe a new mode should be added for test-environments actually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants