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 script mode for Conditions #1798

Merged
merged 1 commit into from
Jan 7, 2020

Conversation

cezkuj
Copy link
Contributor

@cezkuj cezkuj commented Jan 1, 2020

Changes

Allows to use simplified way of creating shell script, same as for Tasks.
Fixes #1694

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

Add script mode for Conditions

@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Jan 1, 2020
@tekton-robot tekton-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 1, 2020
@tekton-robot
Copy link
Collaborator

Hi @cezkuj. 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.

@cezkuj
Copy link
Contributor Author

cezkuj commented Jan 1, 2020

/assign @dlorenc

@dibyom
Copy link
Member

dibyom commented Jan 6, 2020

/ok-to-test

@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 Jan 6, 2020
@tekton-robot
Copy link
Collaborator

The following is the coverage report on pkg/.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
test/builder/condition.go 100.0% 91.7% -8.3

Copy link
Member

@dibyom dibyom left a comment

Choose a reason for hiding this comment

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

Thanks for picking this up @cezkuj 😄

Looking good...just a couple of minor things around examples and docs
/approve

The container image runs till completion. The container must exit successfully i.e. with an exit code 0
for the condition evaluation to be successful. All other exit codes are considered to be a condition check
failure.
Similar to `Task` the check also supports [`script` mode](./tasks.md#step-script). The container image runs
Copy link
Member

Choose a reason for hiding this comment

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

I think it would make sense to say something along the lines of: "The check must specify a Step (link to Step docs)" as opposed to keeping references to the container image/contract.

@@ -41,5 +41,13 @@ func (cs *ConditionSpec) Validate(ctx context.Context) *apis.FieldError {
if cs.Check.Image == "" {
return apis.ErrMissingField("Check.Image")
}
if cs.Check.Script != "" {
Copy link
Member

Choose a reason for hiding this comment

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

If you are feeling motivated, it might be worth seeing if we can reuse the validateSteps function from task_validation.go here as well: https://github.com/tektoncd/pipeline/blob/master/pkg/apis/pipeline/v1alpha1/task_validation.go#L169

Copy link
Contributor Author

@cezkuj cezkuj Jan 7, 2020

Choose a reason for hiding this comment

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

I reused it "as is", validation error is not ideal, as it mentions steps - up to you if we want it improve it further

test/builder/condition.go Show resolved Hide resolved
@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 6, 2020
Allows to use simplified way of creating shell script, same as for Tasks.
Fixes tektoncd#1694
@cezkuj cezkuj requested a review from dibyom January 7, 2020 22:31
Copy link
Member

@dibyom dibyom 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 Jan 7, 2020
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

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

@tekton-robot tekton-robot merged commit f8d6557 into tektoncd:master Jan 7, 2020
@pritidesai
Copy link
Member

Thanks for adding this support 👍

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. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit 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/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

enable script for conditions
6 participants