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

Render pipeline failure should block package push to remote #145

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

Catalin-Stratulat-Ericsson
Copy link
Contributor

@Catalin-Stratulat-Ericsson Catalin-Stratulat-Ericsson commented Nov 26, 2024

Tackles #818 and potentially #658.
The main change this PR proposes is that a package who's render pipeline has failed during a [porchctl rpkg push] should not be allowed to go further into git.
There are fundamental issues with the package in this scenario and can lead to more issues down the line for example in #818.
They should be handled by the user on the local version and retry should be attempted until the package's kpt function pipeline succeeds.

@liamfallon
Copy link
Member

Looks good but it's a bit light on tests ;-)

@Catalin-Stratulat-Ericsson
Copy link
Contributor Author

Catalin-Stratulat-Ericsson commented Nov 27, 2024

Looks good but it's a bit light on tests ;-)

Yes i thought so too. ill have a look now and add extra test where needed. in my eyes 3 things must be tested with this push.

  1. [porchctl rpkg push] when a successful render occurs and package should be pushed to git.
  2. [porchctl rpkg push] when a the object has been modified (aka were trying to push a pkg that is not working off the latest version) & package should not be pushed to git.
  3. [porchctl rpkg push] when a render fails package should not be pushed to git.

let me know if i am missing anything :)

pkg/task/generictaskhandler.go Outdated Show resolved Hide resolved
pkg/task/generictaskhandler.go Outdated Show resolved Hide resolved
pkg/task/generictaskhandler.go Outdated Show resolved Hide resolved
pkg/task/generictaskhandler.go Outdated Show resolved Hide resolved
pkg/task/generictaskhandler.go Outdated Show resolved Hide resolved
pkg/task/generictaskhandler.go Outdated Show resolved Hide resolved
pkg/task/generictaskhandler.go Outdated Show resolved Hide resolved
pkg/task/generictaskhandler.go Outdated Show resolved Hide resolved
@Catalin-Stratulat-Ericsson
Copy link
Contributor Author

/test presubmit-nephio-go-test

@JamesMcDermott
Copy link
Contributor

/approve

Copy link
Contributor

nephio-prow bot commented Nov 27, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Catalin-Stratulat-Ericsson, JamesMcDermott
Once this PR has been reviewed and has the lgtm label, please assign s3wong for approval by writing /assign @s3wong in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@liamfallon
Copy link
Member

Looks good but it's a bit light on tests ;-)

Yes i thought so too. ill have a look now and add extra test where needed. in my eyes 3 things must be tested with this push.

1. [porchctl rpkg push] when a successful render occurs and package should be pushed to git.

2. [porchctl rpkg push] when a the object has been modified (aka were trying to push a pkg that is not working off the latest version) & package should not be pushed to git.

3. [porchctl rpkg push] when a render fails package should not be pushed to git.

let me know if i am missing anything :)

They would be good to have.

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