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

Update some more example links and move task results example #2148

Merged
merged 1 commit into from Mar 5, 2020
Merged

Update some more example links and move task results example #2148

merged 1 commit into from Mar 5, 2020

Conversation

ghost
Copy link

@ghost ghost commented Mar 3, 2020

Changes

Found a few more links that needed to be updated to point to the new
examples directories.

Moved the task_results_example.yaml into the v1beta1 directory and updated it to include a PipelineRun so that the results are exercised.

See #2145 and #2147 for similar changes.

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.

@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Mar 3, 2020
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 3, 2020
- [Task](../examples/v1alpha1/taskruns/optional-resources.yaml)
- [Cluster Task](../examples/v1alpha1/taskruns/optional-resources-with-clustertask.yaml)
- [Condition](../examples/v1alpha1/pipelineruns/conditional-pipelinerun-with-optional-resources.yaml)
- [Pipeline](../examples/v1alpha1/pipelineruns/demo-optional-resources.yaml)
Copy link
Author

Choose a reason for hiding this comment

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

Wasn't sure about these. Linking from the pipeline resources doc (pipeline resources are remaining alpha) so decided to point at v1alpha1 examples. Could be convinced otherwise, anyone got thoughts on this?

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.

/meow

I guess you part of #2139 gets fixed (at least the link)

@tekton-robot
Copy link
Collaborator

@vdemeester: cat image

In response to this:

/meow

I guess you part of #2139 gets fixed (at least the link)

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 3, 2020
@ghost
Copy link
Author

ghost commented Mar 3, 2020

/test pull-tekton-pipeline-integration-tests

Found a few more links that needed to be updated to point to the new
examples directories.

Moved the task_results_example.yaml into the v1beta1 directory.
@tekton-robot tekton-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 3, 2020
- name: a
value: "2"
- name: b
value: "10"
Copy link
Author

@ghost ghost Mar 3, 2020

Choose a reason for hiding this comment

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

follow up idea: would be neat to add an "expected-output" param that checks whether the final result is the expected number.

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

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

@ghost
Copy link
Author

ghost commented Mar 5, 2020

/test pull-tekton-pipeline-integration-tests

@ghost
Copy link
Author

ghost commented Mar 5, 2020

That test run looks stuck to me.

@tekton-robot tekton-robot merged commit 80e7b85 into tektoncd:master Mar 5, 2020
@ghost ghost mentioned this pull request Mar 5, 2020
3 tasks
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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants