State / what needs to be done?

[fingolfin]

What is the state of this now? What still needs to be done?

• set up some kind of recurring trigger
  • perhaps just a simple time base schedule
  • perhaps it can be modified though to only run if either GAP or the distro changed (resp.: if the container we use changed) -- but I have no idea how that would work (perhaps the workflow updating the docker image could trigger a job here?!)
• better status overview
  • @FriedrichRober and @wucas are working on this, I think?
• ... ??

[FriedrichRober]

Yes, Lucas and I are working on better status overview, although finalization depends on our triggers and whether the configuration (docker, test all, etc.) is static or dependent on trigger.

I also do not know how we can trigger jobs from other repositories in gap-infra?

[fingolfin]

@FriedrichRober what kind of jobs do you want to trigger and why?

I think they added some capabilities to do this some time ago, maybe workflow_call can do it, or another of the event types listed there. @wilfwilson might also know more ;-)

[fingolfin]

See also https://docs.github.com/en/actions/using-workflows/reusing-workflows

[FriedrichRober]

I summarized the current state and plans for status overview in the respective draft pull request #17.

I want to call workflows in this repo from other repos. For example I want to run tests if we add a certain comment for a pull request in the gap repository as it is done in Julia and probably let a bot leave a comment once the tests are finished. But I haven't done anything into this direction yet.

[wilfwilson]

Sorry I haven't got round to responding to this. I will respond and create some issues when I have time again.