Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test suite / ci planning #2

Closed
3 of 4 tasks
vsoch opened this issue Feb 16, 2024 · 0 comments
Closed
3 of 4 tasks

test suite / ci planning #2

vsoch opened this issue Feb 16, 2024 · 0 comments

Comments

@vsoch
Copy link
Member

vsoch commented Feb 16, 2024

We need to, for the test suite:

  • add a matrix of builds (based on flux-sched container bases). Note that not all of them (e.g, bookworm) have the reapi_cli.so shared library, and so we likely need to scope to the newer set that do (and then remove the flux-sched build from CI). test: adding testing matrix for os release matrix #4
  • More standard go tests should be added for modules
  • Would be nice to have some concept of a developer base image (e.g., pull and immediately have the full environment with bindings) but maybe that is not necessary. ci: add docker build environment and deploy #6
  • Release cycle - first a manual push here, eventually a trigger to coincide with upstream ci: add automated release pipeline #5
  • How to handle some number of backwards releases? (likely we can't and can only move forward for when reapi_cli.so is built).

The last bullet (testing modules) we will do as needed, as they are added. The main components of this issue are done, and we even have a first release. Not too shabby!

@vsoch vsoch closed this as completed Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant