With #1103368: Add support for 'atomic' purge-and-resync of repositories in, vc_project needs to respond to the added hooks so that a project's release nodes can recover from a repository being resynchronized from scratch - that is, where all the data in the db is blown away and regenerated, causing the ids in {versioncontrol_labels} to change, meaning the data in {versioncontrol_release_labels} becomes stale.

CommentFileSizeAuthor
#1 1103402-resync-respond.patch3.18 KBsdboyer

Comments

sdboyer’s picture

sdboyer commented
StatusFileSize
new 1103402-resync-respond.patch3.18 KB

Clarification - this is in vc_release, not vc_project.

Untested patch is attached. I'm not sure how well I'm set up locally to be able to test this, as I've never actually created a project-attached repo in my local setup, let alone releases. I'll give it a shot tonight, but posting this in the interim in case somebody else who is set up for it can give it a quick run. Testing it is as simple as running drush vcapi-parse-logs --flush [repo_id] on a repo that's attached to a project and has some releases.

sdboyer’s picture

sdboyer commented
Title: Add support for catching up after a resync from scratch » Add support for catching release nodes back up after a repo resync
Status: Active » Fixed
Issue tags: +needs drupal.org deployment

Got my local environment up for testing. Some minor problems in the patch from #1, but it was basically right. Fixed it, changes are pushed, and we're ready for d.o deployment. Finally!

sdboyer’s picture

sdboyer commented
Issue tags: -needs drupal.org deployment

deployed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.