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.

Sign up for GitHub

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

Jump to bottom

testing svace integration #433

Merged
merged 0 commits into from
Apr 8, 2025
Merged

testing svace integration #433

merged 0 commits into from
Apr 8, 2025

Conversation

himax1991
Copy link
Contributor

Description

testing svace integration

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

testing svace integration

Why do we need it in the patch release (if we do)?

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: ci
type: chore
summary: testing svace integration
impact_level: low

@himax1991 himax1991 force-pushed the testing-svace-integration branch from bcaeb70 to 3042a9a Compare April 1, 2025 13:05
@himax1991 himax1991 force-pushed the testing-svace-integration branch from 3042a9a to 1c8ca11 Compare April 1, 2025 14:37
@himax1991 himax1991 added the analyze/svace Run build with Svace integration label Apr 1, 2025
@himax1991 himax1991 closed this Apr 1, 2025
@himax1991 himax1991 reopened this Apr 1, 2025
@himax1991 himax1991 force-pushed the testing-svace-integration branch from 1c8ca11 to 41b5434 Compare April 1, 2025 20:36
@himax1991 himax1991 force-pushed the testing-svace-integration branch 2 times, most recently from f2fee87 to 5a35654 Compare April 2, 2025 14:51
@himax1991 himax1991 force-pushed the testing-svace-integration branch 2 times, most recently from 3d78bb1 to 3cdc35c Compare April 7, 2025 21:21
@himax1991 himax1991 merged commit 3cdc35c into main Apr 8, 2025
36 of 37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@name212 name212 Awaiting requested review from name212

@sprait sprait Awaiting requested review from sprait

@RomanenkoDenys RomanenkoDenys Awaiting requested review from RomanenkoDenys

@Nikolay1224 Nikolay1224 Awaiting requested review from Nikolay1224

@apolovov apolovov Awaiting requested review from apolovov

@yalosev yalosev Awaiting requested review from yalosev

@ldmonster ldmonster Awaiting requested review from ldmonster

@nabokihms nabokihms Awaiting requested review from nabokihms

@Zhbert Zhbert Awaiting requested review from Zhbert

@vladimirGuryanov vladimirGuryanov Awaiting requested review from vladimirGuryanov

@lazovskiy lazovskiy Awaiting requested review from lazovskiy

@AleksZimin AleksZimin Awaiting requested review from AleksZimin

@aleksey-su aleksey-su Awaiting requested review from aleksey-su

Assignees

@himax1991 himax1991

Labels
analyze/svace Run build with Svace integration area/api-change area/cli area/cloud-provider area/cluster-and-infrastructure area/core area/docs area/kubernetes area/monitoring area/network area/security area/storage area/testing enhancement New feature or request go skip/e2e type/dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@himax1991