Closed wm75 closed 2 years ago
Both in WorkflowHub and in LifeMonitor, a workflow gets updated when the owner submits a new version. However, WorkflowHub runs a daily update routine for all IWC workflows, while we currently don't have that for LifeMonitor. We've started exploring the usage of GitHub apps for this and other tasks, but we're not there yet. We discussed this with @mvdbeek on this in https://github.com/galaxyproject/iwc/pull/53. In the meantime, I've updated all outdated workflows on LifeMonitor:
data-fetching/parallel-accession-download
WorkflowHub id: 137
sars-cov-2-variant-calling/sars-cov-2-consensus-from-variation
WorkflowHub id: 138
sars-cov-2-variant-calling/sars-cov-2-pe-illumina-artic-variant-calling
WorkflowHub id: 110
sars-cov-2-variant-calling/sars-cov-2-variation-reporting
WorkflowHub id: 109
Thanks for reporting this!
Forgot to mention: note that, as long as the (URL of the) GitHub Actions workflow that runs the tests does not change between versions, the (scientific) workflow's test status stays up-to-date even if its version isn't.
Example workflows that have more recent workflowhub versions than what's reported as latest version in LifeMonitor:
wfhub: https://workflowhub.eu/workflows/109?version=5 lifemonitor: https://workflowhub.eu/workflows/109?version=3
wfhub: https://workflowhub.eu/workflows/110?version=7 lifemonitor: https://workflowhub.eu/workflows/110?version=6
This is despite the fact that tests have been executed on the more recent versions and that lifemonitor is aware of these executions.