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

feat: Network Operator release trigger #1203

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Conversation

e0ne
Copy link
Collaborator

@e0ne e0ne commented Dec 2, 2024

We need to start SR-IOV Network Operator release if Network Operator Release pipeline started.

@coveralls
Copy link
Collaborator

coveralls commented Dec 2, 2024

Pull Request Test Coverage Report for Build 12805475081

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 10 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+0.3%) to 60.214%

Files with Coverage Reduction New Missed Lines %
pkg/state/state_hostdevice_network.go 2 78.38%
controllers/nicclusterpolicy_controller.go 8 75.31%
Totals Coverage Status
Change from base Build 12754220074: 0.3%
Covered Lines: 3319
Relevant Lines: 5512

💛 - Coveralls

.github/workflows/release.yaml Outdated Show resolved Hide resolved
.github/workflows/release.yaml Outdated Show resolved Hide resolved
.github/workflows/release.yaml Show resolved Hide resolved
- uses: actions/checkout@v4
with:
token: ${{ secrets.GH_TOKEN_NVIDIA_CI_CD }}
repository: ${{ github.repository_owner }}/sriov-network-operator
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tag will always on master branch here, no?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, we don't use master for sriov fork

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean when you do the tag, which branch you should be in?
'actions/checkout@v4' needs to get the target branch, no?

.github/workflows/release.yaml Outdated Show resolved Hide resolved
rollandf
rollandf previously approved these changes Dec 30, 2024
e0ne added a commit to e0ne/network-operator that referenced this pull request Jan 7, 2025
This is a manual PR until Mellanox#1203 is merged.

Signed-off-by: Ivan Kolodiazhnyi <ikolodiazhny@nvidia.com>
steps:
- uses: actions/checkout@v4
with:
token: ${{ secrets.GH_TOKEN_NVIDIA_CI_CD }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were you able to check that secret was propagated to sriov-network-operator? We had some issues with that on docs CI job

e0ne added a commit to e0ne/network-operator that referenced this pull request Jan 7, 2025
This is a manual PR until Mellanox#1203 is merged.

Signed-off-by: Ivan Kolodiazhnyi <ikolodiazhny@nvidia.com>
rollandf pushed a commit to rollandf/network-operator that referenced this pull request Jan 7, 2025
@e0ne e0ne force-pushed the release-action branch 3 times, most recently from 209a703 to f89df7c Compare January 13, 2025 21:39
@e0ne
Copy link
Collaborator Author

e0ne commented Jan 14, 2025

/retest-nic_operator_helm

Signed-off-by: Ivan Kolodiazhnyi <ikolodiazhny@nvidia.com>
@rollandf rollandf merged commit 6140b53 into Mellanox:master Jan 16, 2025
15 of 16 checks passed
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.

4 participants