simple migration test #2471
Labels
automation
related to automated testing/deployment/packaging etc.
low impact
affects only a small portion of a CDN, and cannot itself break one
new feature
A new feature, capability or behavior
Traffic Ops
related to Traffic Ops
We need a simple test that is ran on PRs to ensure that if a migration file is added it is of a date later than all other migrations in the directory. This is a problem we run into a lot when branches age too long.
The text was updated successfully, but these errors were encountered: