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

cleaning up a unit test InvalidPipelineRuns to use YAML parser #4616

Merged

Conversation

pritidesai
Copy link
Member

@pritidesai pritidesai commented Feb 24, 2022

Changes

Replacing task, pipeline, pipelineRun, objects initialization with the YAMLParser for readability in TestReconcile_InvalidPipelineRuns.

Signed-off-by: pritidesai [email protected]

/kind cleanup

part of issue #4610

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes

NONE

@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Feb 24, 2022
@tekton-robot tekton-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Feb 24, 2022
Replacing task, pipeline, pipelineRun, taskRun objects initialization
with the YAMLParser for readability in TestReconcile_InvalidPipelineRuns

Signed-off-by: pritidesai <[email protected]>
@pritidesai pritidesai force-pushed the issue-4610-InvalidPipelineRuns branch from 989a491 to ed01f57 Compare February 24, 2022 16:28
@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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 25, 2022
@ghost
Copy link

ghost commented Mar 2, 2022

/lgtm

@tekton-robot tekton-robot assigned ghost Mar 2, 2022
@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 2, 2022
@tekton-robot tekton-robot merged commit b4f1247 into tektoncd:main Mar 2, 2022
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. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants