search

nextstrain / conda-base

Conda package build for nextstrain-base
https://anaconda.org/Nextstrain/nextstrain-base
1 stars 1 forks source link

Routinely test that the latest package version is initially installable #41

Closed tsibley closed 12 months ago

tsibley commented 1 year ago

From https://github.com/nextstrain/monkeypox/issues/177#issuecomment-1703359429:

So assuming that rebuild mostly* resolves the issue for now, how do we avoid similar issues in the future?

One way might be having scheduled CI in conda-base that regularly tests if the latest package version is still initially installable (similar to how Nextstrain CLI regularly tests if its standalone installers still work, since they're also dependent on external resources). If that test breaks, we get an early warning to see what's up. If we're really fancy, we could potentially even try to detect certain kinds of breakages like this kind here and automatic remediate it by kicking off another package build.

* nextstrain-base versions between (20230717T174555Z, 20230830T164409Z] are still forever broken for initial installs, but could be upgraded to.

This probably looks like a short workflow that, ~every day, does:

- uses: nextstrain/.github/actions/setup-nextstrain-cli@master
  with:
    runtime: conda

on both Linux and macOS.