Date: Wed, 1 Jul 2020 17:51:14 -0400 From: Dan Langille <dan@langille.org> To: freebsd-git@freebsd.org Subject: discovering new commits: FreshPorts Message-ID: <30741857-E21A-4EB9-9C01-81D1E8B8AC03@langille.org>
next in thread | raw e-mail | index | archive | help
FreshPorts currently works off email. Receive a commit email, parse that = email, do some database work. The subversion revision number is contained in the email. That makes it = easy for the code to do: svn up -r X make -V FYI: FreshPorts stores all commits, just not the ports tree. They're all = in there. The technical work of converting a git log message into a FreshPorts = database entry is done: That works. re: https://news.freshports.org/category/development/git/ 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. 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.=20 I don't know how commits arriving in svn relate to commits arriving in = git - will they be there? 2 - repeatedly run 'git fetch origin' to check for new commits We won't miss a thing - but that's rather DDosS-ish. 3 - a commit hook. =20 The git repo hits up a FreshPorts url on each commit. Insights welcomed. =E2=80=94=20 Dan Langille http://langille.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30741857-E21A-4EB9-9C01-81D1E8B8AC03>