Add job for merging OMERO guides

sbesson commented 4 years ago

Implemented a few weeks back to integrate all PRs opened against the various guides and push them to integration branches

joshmoore commented 4 years ago

In general, a huge :+1: for having jobs that to cover all the newer sets of repositories. I do wonder though if a meta-merge job wouldn't spare us some of the difficulties. (This is timely for me since I'm wondering whether or not to go the supermodule root with the various *-zarr-* repositories.)

sbesson commented 4 years ago

A few thoughts on the meta merge job. In general I am in favor of exploring this option and see if it simplifies our workflow moving forward.

A few consideration/difficulties:

generally, the push jobs have more logic than merging PRs and include some coupling in-between the submodules as well as with other push jobs. This is especially true for the Bio-Formats -> OMERO stack.
many coupling push jobs have unified the logic to using https://github.com/ome/build-infra but some of them (BIOFORMATs-build) still have custom code that will need backporting
a single push job will need to define an ordering of the supermodules and handle a shared version.tsv file
in terms of usability, the main downside of the single merge job is probably the daily re-run of a subset of the stack e.g. "just the Bio-Formats jobs". We can discuss strategies on how to deal with this.

The two main routes I can see for testing/driving this idea forward are:

tackle the Bio-Formats -> OMERO-plugin -> OMERO-build -> OMERO-python -> OMERO stack and try to create a single merge job
start with an experimental push job covering all the supermodules which do not require coupling first. Immediately coming to mind: website, management_tools, guides, ansible-roles, docs?

If the latter is the preferred route, I'll start working on this and propose an alternative to #172 and #170

joshmoore commented 4 years ago

Hmm.... good points. Perhaps this is just too large to tackle at the moment (which is probably why it isn't tackled). There's also the question of whether or not GH actions could help with some of this, though I think that might still require putting the coupling logic after the merge/push logic. Happy to keep the conversation going, but we shouldn't block this PR with it.

sbesson commented 4 years ago

Understood, proposing to merge this (and #170), tag and deploy the new jobs in latest-ci in a first instance. Should I turn this conversation into an issue ?

sbesson commented 4 years ago

Tagged as 0.15.5 and merged the tag into merge-ci/latest-ci

ome / devspace

Add job for merging OMERO guides #172