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

Add support for building and running samples and tests in CI that use deprecated features #83701

Open
carlescufi opened this issue Jan 8, 2025 · 1 comment
Assignees
Labels
area: Continuous Integration area: Twister Twister Enhancement Changes/Updates/Additions to existing features

Comments

@carlescufi
Copy link
Member

Is your enhancement proposal related to a problem? Please describe.

The problem is that, when we deprecate a module or subsystem, today we have no way of ensuring that it keeps working during the two release deprecation period. This is because CI fails whenever select DEPRECATED is used in Kconfig (as it should, since we don't want to allow deprecated code to be used in-tree).

Describe the solution you'd like
Extend the {sample,testcase}.yaml format so certain samples and tests can be built and executed even when enabling deprecated features.

Describe alternatives you've considered
Have a special CI build (i.e. twister invocation) that does not fail on deprecation.

Additional context
USB: #42066
TinyCrypt: #82323

@carlescufi carlescufi added the Enhancement Changes/Updates/Additions to existing features label Jan 8, 2025
@carlescufi
Copy link
Member Author

CC @jfischer-no @PavelVPV

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Continuous Integration area: Twister Twister Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

No branches or pull requests

2 participants