Is there any need to do CircleCI testing?

[guyharris]

We have a GitHub action that builds the drafts and updates the corresponding GitHub Pages; does the CircleCi testing provide any benefits not provided by the GitHub action?

Currently, that action is failing with

git -C /tmp/ghpages236 push -qf https://github.com/pcapng/pcapng gh-pages
Password for 'https://****************************************@github.com': make: *** [lib/ghpages.mk:123: ghpages] Hangup

Too long with no output (exceeded 10m0s): context deadline exceeded

which looks suspiciously as if the command

git -C $(GHPAGES_ROOT) push -qf https://$(GITHUB_PUSH_TOKEN)@github.com/$(GITHUB_REPO_FULL) gh-pages >/dev/null 2>&1

in lib/ghpages.mk is timing out because it's asking for a password and nobody supplies it with one. This may be due to the push token being bogus, or something such as that.

It appears that the GitHub Pages are getting updated by the GitHub action, so having CircleCI doesn't appear to be necessary, unless I'm missing something.

[alagoutte]

Hi Guy,

I think it is only historic because there is no GitHub Actions on the origin of this repo...

[mcr]

We can/should do whatever the MT Makefiles use, which I think is now Github actions.