Revert backfill on ci_build_trace_sections
What does this MR do?
We're seeing problems for (small) self-managed instances with the backfill migration for ci_build_trace_sections
. Since we also intend to drop this table anyways (#32565 (closed)), we don't really need to run this migration anymore.
This change disables the migration and actively removes the backfill (batched background) migration if the record is present.
Merge request reports
Activity
changed milestone to %14.2
added Pick into 14.0 Pick into 14.1 groupdatabase typebug labels
assigned to @abrandl
- A deleted user
added databasereview pending label
- A deleted user
added database label
2 Warnings New migrations added but db/structure.sql wasn't updated Usually, when adding new migrations, db/structure.sql should be
updated too (unless the migration isn't changing the DB schema
and isn't the most recent one).You've made some app changes, but didn't add any tests.
That's OK as long as you're refactoring existing code,
but please consider adding any of the tooling, ~"tooling::pipelines", ~"tooling::workflow", documentation, QA labels.Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer database Luis Mejia ( @lmejia2
) (UTC-6, 8 hours behind@abrandl
)Alex Ives ( @alexives
) (UTC-5, 7 hours behind@abrandl
)~migration No reviewer available No maintainer available To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermentioned in issue #32565 (closed)
requested review from @pbair
- Resolved by Andreas Brandl
- Resolved by Andreas Brandl
@abrandl LGTM! I'm approving, but master is still broken at the moment. I'll check back later, otherwise you can merge when your day starts.
added databaseapproved label and removed databasereview pending label
- Resolved by Andreas Brandl
added Engineering Allocation label
added 183 commits
-
9f8fa445...434f40f4 - 181 commits from branch
master
- 27262d7b - Revert backfill on ci_build_trace_sections
- b7caca93 - Turn rollback into no-op
-
9f8fa445...434f40f4 - 181 commits from branch
enabled an automatic merge when the pipeline for d22b3cdd succeeds
mentioned in commit 70f315c3
added workflowstaging label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
picked the changes into the branch
14-1-stable-ee-patch-1
with commit a67a8d73mentioned in commit a67a8d73
Automatically picked into !66726 (merged), will merge into
14-1-stable-ee
ready for14.1.1-ee
.removed Pick into 14.1 label
mentioned in merge request !66726 (merged)
mentioned in merge request !66508 (closed)
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
picked the changes into the branch
14-0-stable-ee-patch-8
with commit 10a5ad9dAutomatically picked into !68761 (merged), will merge into
14-0-stable-ee
ready for14.0.8-ee
.mentioned in commit 10a5ad9d
removed Pick into 14.0 label
mentioned in merge request !68761 (merged)
mentioned in merge request kubitus-project/kubitus-installer!123 (merged)
mentioned in epic &7712
added devopsdata stores label
added groupdatabase frameworks label and removed groupdatabase [DEPRECATED] label
added pipeline:mr-approved label