Open kyleam opened 10 months ago
That makes sense to me. Could we still do this skip if we're querying latest
instead of a version? I'm not sure what exactly that buys us, but I think it probably makes sense.
Also, I assume we'd still do the old frozen version for the "oldest" pipeline, as noted in gh-619?
Could we still do this skip if we're querying
latest
instead of a version? I'm not sure what exactly that buys us, but I think it probably makes sense.
Yes, we could still run that once we got the latest version for via the api.github.com query.
(In terms of what it buys us, the comment following that makes me think it doesn't save us from many installs, but I'd need to look through the drone config and probably read up on some settings to have a better guess.)
Also, I assume we'd still do the old frozen version for the "oldest" pipeline, as noted in gh-619?
Right.
We've moved to GitHub Actions, but this still applies. However, the core implementation would now be in the metrumresearchgroup/actions repo:
inputs:
# TODO: At some point, it'd be nice if the default was to
# automatically detect new versions (bbr 620).
version:
description: Version of bbi to install
It'd be nice if we didn't have to update the drone config for each release (e.g., gh-619). We could update install_bbi.sh to query https://api.github.com/repos/metrumresearchgroup/bbi/releases/latest, though we'd need handling for if the rate limit is hit (especially if we aren't using an authenticated user).