Closed rhybrillou closed 5 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
/kind feature
/test pull-catalog-catlin-lint
@vinamra28: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test pull-tekton-catalog-build-tests
/test pull-tekton-catalog-integration-tests
/test pull-tekton-catalog-unit-tests
Use /test all
to run all jobs.
/retest
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vdemeester, vinamra28
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/test pull-catalog-catlin-lint
@rhybrillou: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test pull-tekton-catalog-build-tests
/test pull-tekton-catalog-integration-tests
/test pull-tekton-catalog-unit-tests
Use /test all
to run all jobs.
/lgtm
/test all
/test pull-catalog-catlin-lint
@vdemeester: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test pull-tekton-catalog-build-tests
/test pull-tekton-catalog-integration-tests
/test pull-tekton-catalog-unit-tests
Use /test all
to run all jobs.
[post-comment : post-comment] Sending this data to GitHub:
[post-comment : post-comment] {'body': ''}
[post-comment : post-comment] Error: 422
[post-comment : post-comment] b'{"message":"Validation Failed","errors":[{"resource":"IssueComment","code":"unprocessable","field":"data","message":"Body cannot be blank"}],"documentation_url":"https://docs.github.com/rest/issues/comments#create-an-issue-comment"}'
Hum.. 🤔
/test pull-tekton-catalog-integration-tests
/test pull-tekton-catalog-integration-tests
FAILED: redhat-dependency-analytics/0-2 task has failed to comeback properly
It might be a legit failure isn't it ?
FAILED: redhat-dependency-analytics/0-2 task has failed to comeback properly
It might be a legit failure isn't it ?
That is correct, but I fear the dependency analytics task is out of my realm. The redhat-dependency-analytics/0.2 task also failed in #1255 and #1257
It might be a legit failure isn't it ?
That is correct, but I fear the dependency analytics task is out of my realm. The redhat-dependency-analytics/0.2 task also failed in #1255 and #1257
But it passed at some point ?
ah yeah it did there..
/test pull-catalog-catlin-lint
@afrittoli: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test pull-tekton-catalog-build-tests
/test pull-tekton-catalog-integration-tests
/test pull-tekton-catalog-unit-tests
Use /test all
to run all jobs.
/test pull-catalog-catlin-lint
@afrittoli: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test pull-tekton-catalog-build-tests
/test pull-tekton-catalog-integration-tests
/test pull-tekton-catalog-unit-tests
Use /test all
to run all jobs.
/test pull-catalog-catlin-lint
@afrittoli: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test pull-tekton-catalog-build-tests
/test pull-tekton-catalog-integration-tests
/test pull-tekton-catalog-unit-tests
Use /test all
to run all jobs.
Changes
Add a generic task for custom interactions with Red Hat Advanced Cluster Security.
This allows users to perform any action with the
roxctl
cli.Submitter Checklist
These are the criteria that every PR should meet, please check them off as you review them:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep[x] Complies with Catalog Organization TEP, see example. Note An issue has been filed to automate this validation
<kind>/<name>/<version>/name.yaml
README.md
at<kind>/<name>/<version>/README.md
metadata.labels
-app.kubernetes.io/version
the same as the<version>
of the resourcemetadata.annotations
tekton.dev/pipelines.minVersion
[x] mandatory
spec.description
follows the conventionSee the contribution guide for more details.