CI: All release platforms should have weekly builds & tests #711
Labels
bug
Something isn't working
Comments
|
@DanGhita @JanMa nodejs/build#2876 will be interesting for v2.2.0 assuming #739 is finished. I think what will need to happen is we build the UI once in an earlier stage and then depend on it from cache for all other arches. |
|
@JanMa @DanGhita Hmm, perhaps problematic, but if we continue to use the matrix form, we'll be limited by https://github.com/gotestyourself/gotestsum/releases , which doesn't support Windows for one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As seen in #700 and #710, we need CI to verify all release platforms at least weekly and ideally be triggerable on demand prior to release. Tests using Docker need not pass (though, ideally, an external Docker host should be provided on platforms which don't have native Docker support), but the binaries should be buildable on these platforms.
As seen with Solaris, if a platform lacks support for OpenBao and its dependencies, it may be dropped from certain releases.
The following platforms and architectures are proposed for mandatory release support:
Pending support in our CI pipelines, the following will be added to mandatory release support:
If anyone would like to volunteer to bring a CI platform, please comment here or otherwise reach out!
The text was updated successfully, but these errors were encountered: