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.
I'm working on #781246: Write Git-specific packaging plugin for d.o but due to problems with how git-dev.d.o is currently configured and confusion about how everything's really going to live on the filesystem, I can't actually write that patch in a way that's going to work when we launch. For now, it's just going to have to assume it's running on a single host that both has the Drupal root for the site and has a copy of /var/git that works. We should fix this before launch so that it checks out via http:// or git:// and uses stable URLs that aren't going to change.
Comments
Comment #1
eliza411 CreditAttribution: eliza411 commentedsdboyer, not sure how you're grouping the file system issues, but would you update this when that issue gets opened?
Comment #2
dwwSeems like this is blocked on #1038404: Determine an approach to managing git repositories on disk for now. Perhaps others.
Comment #3
sdboyer CreditAttribution: sdboyer commentedNot blocked on that, actually. For now the scripts are perfectly fine relying on the local filesystem path contained in $repo->root. We won't need to revisit for several months after launch, at least. Untagging accordingly.
Comment #4
drummComment #5
drummhttp://cgit.drupalcode.org/drupalorg/tree/drupalorg_project/plugins/rele... is the code I'll be updating.
Comment #6
Damien Tournoud CreditAttribution: Damien Tournoud commented@drumm: if you want to still use
git archive
, the easiest path is probably to:git archive --remote=<URL> ...
, where<URL>
is a simple Git-protocol URL (ie. one withgit://
);git-daemon
on util so that it allows theupload-archive
service.There are two alternative paths, but I don't think they are desirable:
--shallow
) and export the archive from there;Comment #7
drummI think I may go with a variation on
There are some more Git operations that happen for branch packaging in
computeRebuildVersion()
. My testing shows that works with a--depth 0
clone.(I'm also not eager to change the Git daemon config.)
Comment #8
drummActually,
--depth 1
is what I would want for a shallow clone, and it doesn't helpcomputeRebuildVersion()
. That code looks like it needs a full clone locally, or at least the history back to the most recent tag on the branch. We will need to do a full clone anyway.Comment #10
drummComment #11
drummNow deployed.