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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove linting from release pipeline 馃Ч #588

Merged
merged 1 commit into from May 28, 2020

Conversation

bobcatfish
Copy link
Collaborator

Changes

Linting should never fail on a release Pipeline since any issues should
be caught in the PR. This linting is failing in the nightly release
pipeline for unknown reasons so let's remove it. We can keep debugging
the issue if we encounter it again somewhere that we actually need it.

I tested this by manually applying the pipelines and manually triggering
the nightly cron:

k --context dogfood create job --from cronjob/nightly-cron-trigger-triggers-nightly-release nightly-cron-trigger-triggers-nightly-release-manual-05282020

Fixes tektoncd/plumbing#403

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.

Linting should never fail on a release Pipeline since any issues should
be caught in the PR. This linting is failing in the nightly release
pipeline for unknown reasons so let's remove it. We can keep debugging
the issue if we encounter it again somewhere that we actually need it.

I tested this by manually applying the pipelines and manually triggering
the nightly cron:

```
k --context dogfood create job --from cronjob/nightly-cron-trigger-triggers-nightly-release nightly-cron-trigger-triggers-nightly-release-manual-05282020
```

Fixes tektoncd/plumbing#403
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 28, 2020
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.

Thank you! I assume we are also doing this for pipeline and other repos?
/lgtm

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

[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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 28, 2020
@tekton-robot tekton-robot merged commit 99068f0 into tektoncd:master May 28, 2020
@bobcatfish
Copy link
Collaborator Author

I assume we are also doing this for pipeline and other repos?

Good question - its removed from pipelines, maybe it makes sense to do the others as well 馃 Or we could wait until it causes a problem and remove it then?

@bobcatfish
Copy link
Collaborator Author

(that's probably just me being lazy 馃槄 )

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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Triggers nightly release sometimes failing with same strange error
3 participants