-
Notifications
You must be signed in to change notification settings - Fork 335
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
ci(tests): add container structure tests #6581
ci(tests): add container structure tests #6581
Conversation
Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
8135843
to
fc5b054
Compare
Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
…e-tests Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
…e-tests Signed-off-by: Bart Smykla <bartek@smykla.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this just be part of make test
?
I'm not sure. Having it separately is cleaner for me, and I think it's easier to potentially debug. Especially as |
Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Bart Smykla <bartek@smykla.com>
@Mergifyio backport release-2.2 release-2.1 release-2.0 release-1.8 release-1.7 |
✅ Backports have been created
|
* skip arm64 on kuma-commit by default * add entrypoints to structure tests Signed-off-by: Bart Smykla <bartek@smykla.com> (cherry picked from commit 42e4980)
* skip arm64 on kuma-commit by default * add entrypoints to structure tests Signed-off-by: Bart Smykla <bartek@smykla.com> (cherry picked from commit 42e4980) # Conflicts: # .circleci/config.yml # Makefile # mk/dependencies/deps.lock
* skip arm64 on kuma-commit by default * add entrypoints to structure tests Signed-off-by: Bart Smykla <bartek@smykla.com> (cherry picked from commit 42e4980) # Conflicts: # .circleci/config.yml # Makefile # mk/dependencies/deps.lock
* skip arm64 on kuma-commit by default * add entrypoints to structure tests Signed-off-by: Bart Smykla <bartek@smykla.com> (cherry picked from commit 42e4980) # Conflicts: # .circleci/config.yml # Makefile # mk/dependencies/deps.lock # mk/dev.mk
* skip arm64 on kuma-commit by default * add entrypoints to structure tests Signed-off-by: Bart Smykla <bartek@smykla.com> (cherry picked from commit 42e4980) # Conflicts: # .circleci/config.yml # Makefile # mk/dependencies/deps.lock # mk/dev.mk
This is the initial version of this feature as the configurations for structure tests can be improved, to for example test if versions of the binaries are expected (this involve introducing dynamic [containing exact versions] configuration files)
I would prefer to make testing entrypoints declarative, so instead of explicitly checking if its value is equal
X
, to check if i.e. runningdocker run kumahq/kuma-cp:2.2.0 version
works. We can't usecontainer-structure-tests
to achieve it, as it overrides entrypoints, so I decided to accept this compromise. Maybe in the future if there will be need, we can just run commands likedocker run kumahq/kuma-cp:2.2.0 version
in tests directly.syscall.Mkfifo
have equivalent implementation on the other OS --UPGRADE.md
? -- you don't> Changelog:
entry here or add aci/
label to run fewer/more tests?