discovering new commits: FreshPorts

[Ed Maste]

On Wed, 1 Jul 2020 at 17:51, Dan Langille <dan at langille.org> wrote:
>
> The biggest remaining issue: what method should FreshPorts use to start working on a new commit? What process replaces the incoming svn commit email?
>
> At present, there is no email for the git commits (re https://lists.freebsd.org/mailman/listinfo).  It's only the svn commits.

We will have a git commit mailing list by the time we're ready to make
the switch, but indeed it's not there yet.

> I see these choices:
>
> 1- continue to process based upon incoming email, but use that only as the reason to wake up and check git for new commits.
>
> I don't know how commits arriving in svn relate to commits arriving in git - will they be there?

There's usually 0-15 minutes of latency between a commit to svn and
the same change appearing in the (GitHub) git mirror, but sometimes
it's a bit longer. This might work some of the time but isn't going to
be reliable.

> 2 - repeatedly run 'git fetch origin' to check for new commits
>
> We won't miss a thing - but that's rather DDosS-ish.

As long as the polling frequency is not too high this should be fine.

> 3 - a commit hook.
>
> The git repo hits up a FreshPorts url on each commit.

This sounds like the best approach, and I'd be happy for us to add
this to the new git repo config.