Skip to content
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.

Rename Assignment::RepositoryVisibilityJob to a single class #2220

Merged

Conversation

jeffrafter
Copy link
Contributor

Currently we have two definitions of the Assignment class and this tends to break auto-loading in unexpected ways. This PR renames Assignment::RepositoryVisibilityJob to AssignmentRepositoryVisibilityJob making it no-longer-nested. This keeps the concerns of Jobs and Models separate.

Because this PR renames a Job we need to deploy the fix in multiple steps:

  1. Duplicate the job with the new name and start using that new job only
  2. Deploy that change
  3. Wait until the old jobs are out of the queue (and only new jobs are being enqueued)
  4. Remove the old job and deploy

This should fix the Assignment errors which led to today's maintenance mode.

@jeffrafter jeffrafter requested a review from a team August 9, 2019 21:31
@jeffrafter jeffrafter self-assigned this Aug 9, 2019
Copy link
Contributor

@shaunakpp shaunakpp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@jeffrafter jeffrafter requested a deployment to production August 9, 2019 21:36 Abandoned
@jeffrafter jeffrafter merged commit 0d8d28e into master Aug 9, 2019
@jeffrafter jeffrafter deleted the jr-duplicate-and-rename-repository-visibility-job branch August 9, 2019 21:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants