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

Add decorate flag on pull-tekton-experimental-helm-lint #302

Merged
merged 1 commit into from
Apr 8, 2020

Conversation

eddycharly
Copy link
Member

Added decorate: true on pull-tekton-experimental-helm-lint prow job.

@tekton-robot tekton-robot requested review from dibyom and kimsterv April 8, 2020 09:26
@tekton-robot tekton-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 8, 2020
@tekton-robot
Copy link
Contributor

Hi @eddycharly. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 8, 2020
@vdemeester
Copy link
Member

/ok-to-test
/cc @afrittoli

@tekton-robot tekton-robot requested a review from afrittoli April 8, 2020 09:54
@tekton-robot tekton-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 8, 2020
Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

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

/approve

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 8, 2020
Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

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

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2020
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli, vdemeester

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:
  • OWNERS [afrittoli,vdemeester]

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

@tekton-robot tekton-robot merged commit 7afbb78 into tektoncd:master Apr 8, 2020
@bobcatfish
Copy link
Contributor

It's too late to do this in the commit message, but @eddycharly (or @vdemeester if you know) could you explain a bit more about why this flag is needed? i.e. what this adds, and was something broken without it?

Thanks!

@eddycharly
Copy link
Member Author

@bobcatfish it adds decoration to the pod running the job.
That is, it adds some other containers that are responsible of cloning the repository, setting the correct working dir, uploading logs and artifacts etc...

@bobcatfish
Copy link
Contributor

Thanks @eddycharly that helps! I just noticed #305 as well - i mentioned there but having an issue or something that these PRs could link to would help provide some context

I know it's hard to get these prow things working first shot since it's hard to try them out :(

@eddycharly
Copy link
Member Author

You can read more here: https://github.com/kubernetes/test-infra/blob/master/prow/pod-utilities.md

I wrote the job for pipeline agent first but i reverted to kubernetes agent while thinking the pipeline agent was the issue.
In the end the issue was not directly related to the agent, i could try to use pipeline agent again but i fear logs would not be uploaded.

@bobcatfish
Copy link
Contributor

Thanks @eddycharly that helps too!

What I mean though is the context for adding pull-tekton-experimental-helm-lint which I assume you are working toward adding with these PRs? (Basically I have to guess the context for this work at the moment, maybe I'm wrong)

@eddycharly
Copy link
Member Author

Working towards #306.

@bobcatfish i created the issue, linking it in the PRs for history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants