Skip to content

Conversation

@diafour
Copy link
Member

@diafour diafour commented Jan 26, 2026

Description

  • Add build command to run svace analyzer over bounder image.

Why do we need it, and what problem does it solve?

We need all images to be in svace reports. Even trivial ones as bounder.

What is the expected result?

'bounder' image is in the svace report.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: module
type: chore
summary: Add bounder image to svace report.

- Add build command to run svace analyzer over bounder image.

Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
@diafour diafour merged commit 241e930 into main Jan 26, 2026
27 of 28 checks passed
@diafour diafour deleted the chore/module/svace-analyze-for-bounder branch January 26, 2026 16:40
universal-itengineer pushed a commit that referenced this pull request Jan 27, 2026
* chore(module): add bounder to svace analyze process

- Add build command to run svace analyzer over bounder image.


Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
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

Successfully merging this pull request may close these issues.

3 participants