Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.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.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 1103402-resync-respond.patch | 3.18 KB | sdboyer |
Comments
Comment #1
sdboyer CreditAttribution: sdboyer commentedClarification - 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.Comment #2
sdboyer CreditAttribution: sdboyer commentedGot 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!
Comment #3
sdboyer CreditAttribution: sdboyer commenteddeployed