-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Monitoring implementation comes from discussion during the OME 2025 meeting
- Option 1 (current implementation):
- Monitor the output of the GitHub workflows run on the repositories specified in
repositories.json
. It is possible to monitor all the workflows run against the default branch (default) or to specified the workflow(s) to monitor. The repositories monitor should run daily (not the case atm). This repository will keep the output of the runs for 30 days.
- Monitor the output of the GitHub workflows run on the repositories specified in
- Option 2a:
- Declare the repositories to monitor
- Trigger a build in each repository specified in
repositories.json
via Publisher/subscriber approach in GitHub actions - This approach is more intrusive, each repository
- must handle an event see https://github.com/jburel/omero-cli-transfer/blob/main/.github/workflows/omero_plugin.yml#L22 and
- add user with correct permissions to the repository. This option is not possible for jax i.e. not possible to add user
- Option 2b:
- Same as 2a but in that case, the repositories should be forked by snoopycrimecop and the output collected from the workflows run from the snoopycrimecop account. This will avoid the permissions raised in 2a but it means that the repos need to be kept in synch
Metadata
Metadata
Assignees
Labels
No labels