forked from tektoncd/pipeline
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove linting and unit tests from release pipelines 🧹
This might be a controversial choice but I think our release Pipelines should only include Tasks that we expect to give us useful feedback about the release. Unit tests and linting should fail on pull requests; if they fail on a release this means one of two things: 1. The linting/test didn't actually run against the merged version of the pull request 2. There is something flakey in the linting/test In the case of (1) this means the pull request shouldn't have actually been merged, and this failing at release time means anyone looking at the releases will now be responsible for fixing this pull request's problems, therefore we should be sure to run this on the pull request before actually merging (this is I think what Tide is responsible for). In the case of (2), why should this block a release? So I think we should remove these steps entirely, especially in light of tektoncd/plumbing#241 making these flake. (I think we could remove "build" from this as well since it's not actually used to build the resulting artifact, and the step that actually does build the artifact would fail anyway.)
- Loading branch information
1 parent
255e8d8
commit cba3ddf
Showing
3 changed files
with
2 additions
and
71 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters