-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Add cold storage option on builds & configurable BuildViewSet #3147
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
Conversation
name='cold_storage', | ||
field=models.BooleanField(default=False, help_text='Build comamnds are stored outside the database.', verbose_name='Cold Storage'), | ||
), | ||
migrations.AlterField( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All this was added automatically, I think small updates that we haven't migrated on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, i get some of these too. Lets remove them from here and figure out which of these migrations are required now. We might need to roll a fresh db locally to figure that out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I've been removing extraneous migration operations from my migrations until i get back to testing which of these are actually required against a fresh database. I only get some of these on my instance when building new migrations.
name='cold_storage', | ||
field=models.BooleanField(default=False, help_text='Build comamnds are stored outside the database.', verbose_name='Cold Storage'), | ||
), | ||
migrations.AlterField( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, i get some of these too. Lets remove them from here and figure out which of these migrations are required now. We might need to roll a fresh db locally to figure that out.
No description provided.