Related to #1401990: Record a 'rebuild_version' for release nodes that are rebuilt but a bit different...

It'd be nice for versioncontrol_release to remember the exact VCAPI revision string that was used to package a given release. In the d.o case, this would be the exact git commit hash -- equivalent to #1360474: Record the exact git hash checked out in -dev releases into the packaged .info files but instead of the packaging script just storing it in the .info files, it could also tell versioncontrol_release about it so it can record it in the DB for future use...

sdboyer warned me about the fact that the repos are sometimes flushed and re-parsed, e.g. when folks want to change the authorship info to associate commits with the right account or something. In that case, all the commit hashes can change. Luckily, there's a hook that gets invoked in this case, and we should be able to respond to that operation inside versioncontrol_release_versioncontrol_repository_pre_resync() and somehow re-map the hashes as needed...

Comments

dww’s picture

Status: Active » Closed (won't fix)

After a fairly lengthy IRC chat with sdboyer, my professional opinion is now "SCREW THAT!" ;)

- We don't actually have any valid use-case for why we want this. It's just "maybe someone will find it useful".
- There are all sorts of potential complications, like what happens if a repo has to be rebuilt and the hashes change?

We all have vastly more important things to work on than solving hairy problems for things we doubt we'll ever use.

Hence, won't fix...