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

refactor(config/jobs): run peribolos against org.yaml in evolution repo #1000

Closed
wants to merge 2 commits into from

Conversation

maxgio92
Copy link
Member

@maxgio92 maxgio92 commented Feb 15, 2023

This PR updates the Peribolos job to support org.yaml Github organization declarative configuration file, versioned in evolution.

Additional info

IMPORTANT: it needs first the points below in place:

Superseedes #841.

@poiana
Copy link
Contributor

poiana commented May 20, 2023

@maxgio92: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
validate-new-drivers-ubuntu-gke-5-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-gke-5-presubmit
validate-new-drivers-minikube-presubmit 4c48387 link true /test validate-new-drivers-minikube-presubmit
validate-new-drivers-ubuntu-azure-3-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-azure-3-presubmit
validate-new-drivers-ubuntu-gcp-4-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-gcp-4-presubmit
validiate-new-drivers-fedora-presubmit 4c48387 link true /test validiate-new-drivers-fedora-presubmit
validate-new-drivers-ubuntu-azure-4-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-azure-4-presubmit
validate-new-drivers-ubuntu-aws-3-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-aws-3-presubmit
validate-new-drivers-ubuntu-aws-4-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-aws-4-presubmit
validate-new-drivers-ubuntu-generic-3-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-generic-3-presubmit
validate-new-drivers-ubuntu-gke-3-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-gke-3-presubmit
validate-new-drivers-ubuntu-generic-4-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-generic-4-presubmit
validate-new-drivers-ubuntu-azure-5-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-azure-5-presubmit
validiate-new-drivers-debian-presubmit 4c48387 link true /test validiate-new-drivers-debian-presubmit
validate-new-drivers-ubuntu-aws-5-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-aws-5-presubmit
validate-new-drivers-centos-6-presubmit 4c48387 link true /test validate-new-drivers-centos-6-presubmit
validate-new-drivers-ubuntu-azure-6-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-azure-6-presubmit
validate-new-drivers-ubuntu-gke-6-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-gke-6-presubmit
validate-new-drivers-ubuntu-gcp-6-presubmit 4c48387 link true /test validate-new-drivers-ubuntu-gcp-6-presubmit
valdiate-new-drivers-ubuntu-generic-6-presubmit 4c48387 link true /test valdiate-new-drivers-ubuntu-generic-6-presubmit
validiate-new-drivers-almalinux-presubmit 4c48387 link true /test validiate-new-drivers-almalinux-presubmit
validate-new-drivers-fedora-presubmit 4c48387 link true /test validate-new-drivers-fedora-presubmit
validate-new-drivers-almalinux-presubmit 4c48387 link true /test validate-new-drivers-almalinux-presubmit
validate-new-drivers-debian-presubmit 4c48387 link true /test validate-new-drivers-debian-presubmit
validate-new-drivers-talos-presubmit 4c48387 link true /test validate-new-drivers-talos-presubmit

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@maxgio92
Copy link
Member Author

/retest

@maxgio92 maxgio92 force-pushed the refactor/orgyaml-in-evolution-reop branch from 4c48387 to ef1d917 Compare June 21, 2023 13:31
@maxgio92
Copy link
Member Author

JFI: I updated the org.yaml file paths, according to https://github.com/falcosecurity/evolution/pull/274/files

@maxgio92
Copy link
Member Author

/hold

until falcosecurity/evolution#274 is ready

Copy link
Contributor

@FedeDP FedeDP left a comment

Choose a reason for hiding this comment

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

/lgtm

Copy link
Contributor

@FedeDP FedeDP left a comment

Choose a reason for hiding this comment

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

/approve

@poiana
Copy link
Contributor

poiana commented Jun 21, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FedeDP, maxgio92

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

The pull request process is described 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

@poiana
Copy link
Contributor

poiana commented Sep 19, 2023

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

@poiana
Copy link
Contributor

poiana commented Oct 19, 2023

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

@poiana
Copy link
Contributor

poiana commented Nov 18, 2023

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana poiana closed this Nov 18, 2023
@poiana
Copy link
Contributor

poiana commented Nov 18, 2023

@poiana: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants