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

Make CI using downstream integrations optional #353

Open
baentsch opened this issue Feb 24, 2024 · 0 comments
Open

Make CI using downstream integrations optional #353

baentsch opened this issue Feb 24, 2024 · 0 comments
Labels
enhancement New feature or request futurework This may or may not be worked on good first issue Good for newcomers

Comments

@baentsch
Copy link
Member

CI of this project also uses downstream packaging of liboqs (apt and brew) to test the integrity of the code base. This fails when a feature not yet packaged up downstream (ML-* in this case) is used.

This issue therefore proposes to make such tests optionally selectable, e.g. by environment variable, such as to permit CI to be adapted to the progress outside of the control of this project.

As usual, other proposals to resolve welcome.

@baentsch baentsch added the good first issue Good for newcomers label Mar 30, 2024
@baentsch baentsch added enhancement New feature or request futurework This may or may not be worked on labels May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request futurework This may or may not be worked on good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant