-
Notifications
You must be signed in to change notification settings - Fork 141
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
Add the new git-clone-oci-ta Task #1005
Conversation
Tip for reviewers: the first commit in this PR is a plain copy of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with one nitpick
This commit creates a copy of the git-clone directory in the git-clone-oci-ta directory. This is done to make it easier to review the corresponding changes to support Trusted Artifacts. Signed-off-by: Luiz Carvalho <[email protected]>
Signed-off-by: Luiz Carvalho <[email protected]>
0b8db1c
to
96de586
Compare
Ref: EC-550 Co-authored-by: Zoran Regvart <[email protected]> Signed-off-by: Luiz Carvalho <[email protected]>
Quality Gate passedIssues Measures |
/retest |
/retest Seems like an unrelated issue:
|
/retest |
Side note: these changes should have no impact on the existing tasks and pipelines. e2e-tests errors are likely unrelated. |
/retest |
Weird e2e failure...
We should probably just merge this PR as is. I can't think of how adding a new Task would cause issues on that test |
I'm force merging this after Luiz pinged me about it. Neither of us could reason that adding a new task would cause CI to fail in that way. Build team - if you would rather I not use admin powers to do this in the future, please reach out and let me know and I'll adjust. |
FWIW, the e2e-tests failures seem to be due to too many secrets linked to the ServiceAccount:
I was able to get this in Splunk from one of the Tasks in the failing test pipeline:
|
This pull request introduces a new Tekton Task,
git-clone-oci-ta
. This is a variation of the0.1/git-clone
Task. The main difference is that instead of cloning to a workspace, this Task stores the cloned repository as a Trusted Artifact in an OCI registry.The Task is not currently used in any of the default Pipelines. This will happen later on.
I tested this Task on a kind cluster like this:
Resolves EC-550