It would really help people to start to use the git.drupalcode.org repo if it refreshed far more often.

My suggestion:

Somehow make a post-commit hook trigger a rebuild of the project (probably for contrib only) so that people would have to wait very little time to find their commit reflected in the git repo. The regular overall rebuild could still be done just as it is now.

Thanks,
-Randy

Comments

sdboyer’s picture

sdboyer commented
Issue tags: +git phase 2

Tagging

jbrown’s picture

jbrown commented

This would be very awesome!

sdboyer’s picture

sdboyer commented
Assigned: Unassigned » sdboyer
Issue tags: +git sprint 3

see if we can't do this for the sprint after this one. this'd be really great to have, would help people to rely a bit more on git.drupalcode.org

neclimdul’s picture

neclimdul
He/Him
commented

sub

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

I think we should try to get this done, just for ourselves, because we're all frustrated about it.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Title: Please make a commit cause a rebuild on a contrib project » Rebuild git projects more frequently if there are commits

I have suggested one way to do this, but the real issue here is that we need to see the git repo update more often, because it's not fast enough for real development.

The reason to do this (long) before rollout is:

  • We want people to use the repositories both to get them in the habit
  • If we get them using it, we'll have high confidence at rollout that the repos are solid.

mikey_p and others have proposed other approaches like checking the db every minute or two for commits, and doing a project rebuild.

And of course, the full rebuild every 2 hours would still supercede any project rebuilds.

dww’s picture

dww
we/he/they
commented

I'd strongly recommend not touching the existing xcvs hooks for this. They're fragile, and we don't have the time to afford to maybe break them and clean up the resulting mess. I'd be much happier if something was just watching the {cvs_files} table or something like that.

I'm neutral on if this is worth doing at all. It seems we have a lot of other work that needs to happen to make the Git migration a reality, things that need to happen. This is optional, and therefore, seems really low priority to me (or won't fix). But if we're going to do this, I'm strongly opposed to triggering it directly inside the xcvs scripts themselves.

Cheers,
-Derek

sdboyer’s picture

sdboyer commented
Issue tags: +git sprint 6

neclimdul knocked this sucker out. It's now running live - CVS commits to projects are reflected within 5 minutes on git.drupalcode.org. woohoo!

sdboyer’s picture

sdboyer commented
Status: Active » Fixed
rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

Yippee! SO very cool! I think this is a win for the project.

We need to publicize this so that people know they can switch over.

Status: Fixed » Closed (fixed)
Issue tags: -git phase 2, -git sprint 3, -git sprint 6

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

Issue tags: +git phase 2, +git sprint 3, +git sprint 6

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.