Trigger Open Project site CI deployments automatically on each software/spec repo update

[strogonoff]

Currently in OP framework, each project site during its build pulls the information about each descendant software package from that package’s GitHub repo (things like last commit timestamp, documentation, soon probably latest release & other things).

This keeps things more or less DRY, and maintainers don’t need to make commits to project sites each time any of its descendant software packages gets updated.

However, it is still preferable to build project sites when software gets updated so that sites show up-to-date commit timestamps, docs & all. While we do have the CI set up, without a commit in project site repo the site won’t get built.

I see two options:

• Automatic way: As we use Travis CI now, it can be pretty straightforward to set up GitHub webhooks on software packages repos so that they ping Travis API for their respective project sites builds whenever a new commit lands for any given software. This way we’ll remove one of the few remaining cases where human participation is needed in Open Project site lifecycle.

• Semi-automatic way: Let site maintainers trigger site builds via Travis dashboard (I don’t think I can do this currently).

Those options are not mutually exclusive, ideally both would be good. Also, in either case we might want to debounce build triggers to ensure they don’t queue up, unless Travis does that natively.

[ronaldtse]

@strogonoff could you help implement the first option first?

And in the deployment job of the OP site we can set Travis to debounce builds too.

[ronaldtse]

Methods to achieve the first option:

• https://hiddentao.com/archives/2016/08/29/triggering-travis-ci-build-from-another-projects-build/
• https://stackoverflow.com/questions/47293851/is-it-possible-to-have-travis-ci-trigger-another-repositorys-build

[strogonoff]

@ronaldtse Doing a pilot of this on Metanorma site.

When available, could you please do the following:

1. Run travis login && travis token
2. In Travis settings for metanorma.com, create a variable TRAVIS_ACCESS_TOKEN containing the access token shown on previous step. According to how Travis works, variable contents would be visible only to you and won’t be included in logs
3. Run Travis build to check for failures. (Open hub build should also get triggered)

[strogonoff]

(For now to trigger the build we’re using a third-party script downloaded from GitHub each build, as suggested by some of the links posted by Ronald. If the pilot is successful we might/should switch to hosting the triggering code under our control to avoid unexpected surprises.)

[strogonoff]

@ronaldtse Feel free to ignore this, apparently I have Travis dashboard access for metanorma.com!

[ronaldtse]

Yay! Sorry I completely missed this issue... 😭

[strogonoff]

Current status:

• [x] Triggering build project site repo -> hub site repo
• [ ] Triggering build software or spec repo -> project site and hub site repos
• [ ] Avoiding relying on third-party triggering code for sanity & security