Travis CI builds have been disabled about catalog

[dhimmel]

Okay I set up the repository dispatch in 48d40a4 and manubot/manubot.org@6ec28ef. I renamed @manubot-catalog-travis-bot to @manubot-org-bot, which is a GitHub account that only has write access to https://github.com/manubot/manubot.org. This way we don't have to worry about the broad scope of the repo PATs.

See the CI builds at

• https://github.com/manubot/catalog/runs/2816241539#step:7:1
• https://github.com/manubot/manubot.org/runs/2816262716

Slight worry that there is not enough of a delay, such that https://manubot.github.io/catalog/catalog.json won't have started serving the new data yet. Will see if this is a problem.

[dhimmel]

More info on the change at https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

[agitter]

we will have to look into having this action trigger the website action

A quick search gave a few leads:

• workflow dispatch event
• repository dispatch event (blog post 1, blog post 2)
• Actions that build upon these events.

The peter-evans/repository-dispatch action looks like the best choice initially because it is maintained and supports a payload. aurelien-baudet/workflow-dispatch has support to wait for an workflow triggered in another repository to complete, which is a nice feature but not needed here. ph-fritsche/action-dispatch supports workflow or repository events. GitHub describes the difference as

You can manually trigger workflow runs. To trigger specific workflows in a repository, use the workflow_dispatch event. To trigger more than one workflow in a repository and create custom events and event types, use the repository_dispatch event.

We'll eventually need to migrate the other manubot organization repositories as well: https://travis-ci.com/github/manubot

[dhimmel]

I switched this repo and the website to GitHub Actions and revoked the Travis CI permissions for those repos. See the GitHub workflows at:

• https://github.com/manubot/catalog/blob/46cf095c563f828105fdf47d18b17895a77ed5a9/.github/workflows/build.yaml
• https://github.com/manubot/manubot.org/blob/8f6a366251f58043527d71546c78a01ccd4b5bc5/.github/workflows/build.yaml

Both workflows are scheduled to run once per week. I scheduled the manubot.org build to be an hour after the catalog build. Currently, did not set up repository dispatch.

The manubot.org job is super fast (40 seconds), so we could schedule it daily. It was nice to have the website update quickly after a manuscript is added. So perhaps we should look into repository dispatch.

[agitter]

This is a nice solution. Using the GitHub Pages action instead of the deploy script simplifies the workflow considerably.

If we change the manubot.org builds to run daily, that would be a reasonable alternative to repository dispatch-triggered builds. Triggered builds would be easy to set up now that you've switched both workflows the GitHub Actions. The only downside is that we would need to add a personal access token instead of using the GITHUB_TOKEN .