Skip to content

Re-enqueue epic cache counts update

Jan Provaznik requested to merge jp-cache-counts-sched into master

What does this MR do and why?

Cache count updates seem to finally work as expected. We do final update of existing epics to assure we have up-to-date correct data.

This MR also makes previous migrations (which scheduled cache count update) no-op - the reason is that the newly scheduled migration does the same job.

Related to #378907 (comment 1272467096)

DB migration output

honza@pc ~/gitlab-development-kit/gitlab (jp-cache-counts-sched)$ rake db:rollback:main db:rollback:ci
WARNING: This version of GitLab depends on gitlab-shell 14.17.0, but you're running 14.15.0. Please update gitlab-shell.
main: == 20230209131808 RecountEpicCacheCountsV3: reverting =========================
main: == 20230209131808 RecountEpicCacheCountsV3: reverted (0.0230s) ================

ci: == 20230209131808 RecountEpicCacheCountsV3: reverting =========================
ci: -- The migration is skipped since it modifies the schemas: [:gitlab_main].
ci: -- This database can only apply migrations in one of the following schemas: [:gitlab_ci, :gitlab_shared, :gitlab_internal].
ci: == 20230209131808 RecountEpicCacheCountsV3: reverted (0.0074s) ================

honza@pc ~/gitlab-development-kit/gitlab (jp-cache-counts-sched)$ rake db:migrate
WARNING: This version of GitLab depends on gitlab-shell 14.17.0, but you're running 14.15.0. Please update gitlab-shell.
main: == 20230209131808 RecountEpicCacheCountsV3: migrating =========================
main: == 20230209131808 RecountEpicCacheCountsV3: migrated (0.0829s) ================

ci: == 20230209131808 RecountEpicCacheCountsV3: migrating =========================
ci: -- The migration is skipped since it modifies the schemas: [:gitlab_main].
ci: -- This database can only apply migrations in one of the following schemas: [:gitlab_ci, :gitlab_shared, :gitlab_internal].
ci: == 20230209131808 RecountEpicCacheCountsV3: migrated (0.0103s) ================

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Jan Provaznik

Merge request reports