You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This workflow automatically runs integration tests for any Tekton Task that is changed in a pull request. It spins up a temporary Kubernetes (Kind) cluster, deploys Tekton, and then executes the tests defined for the modified task.
207
+
To ensure all Tekton Tasks are well-formed and valid, a single `Run Task Tests` workflow is executed on every pull request that modifies files in the `task/` directory.
208
+
209
+
This workflow is designed to be efficient by following a two-stage logic:
210
+
211
+
1.`Syntax Validation`
212
+
2.`Integration Tests`
207
213
208
214
#### How to Add a Test
209
215
@@ -288,22 +294,6 @@ Using `$(params.*)` directly in a script creates a security flaw. Tekton perform
288
294
289
295
For more details and guidance on fixing the issue, see the [Tekton recommendations](https://github.com/tektoncd/catalog/blob/main/recommendations.md#dont-use-interpolation-in-scripts-or-string-arguments)
290
296
291
-
### Tekton Task Validation
292
-
293
-
To ensure all Tekton Tasks are well-formed and valid, a `Check Tekton Tasks` workflow is executed on every pull request. This workflow serves as a safeguard to block invalid tasks from being merged, so we don’t risk breaking users.
294
-
295
-
#### If the Check Fails
296
-
297
-
- Open the workflow logs in GitHub Actions
298
-
- Look at the `Apply all Tasks` step
299
-
- The logs will show which Task file failed and the exact error
300
-
301
-
> [!NOTE]
302
-
> The `setup-tektoncd` step may occasionally fail due to GitHub API `rate limits` (see [tektoncd/actions#9](https://github.com/tektoncd/actions/issues/9)).
303
-
> This is a known issue and not related to your changes.
304
-
>
305
-
> The current workaround is to `re-run the workflow`.
This workflow automatically runs integration tests for any Tekton Task that is changed in a pull request. It spins up a temporary Kubernetes (Kind) cluster, deploys Tekton, and then executes the tests defined for the modified task.
207
+
To ensure all Tekton Tasks are well-formed and valid, a single `Run Task Tests` workflow is executed on every pull request that modifies files in the `task/` directory.
208
+
209
+
This workflow is designed to be efficient by following a two-stage logic:
210
+
211
+
1.`Syntax Validation`
212
+
2.`Integration Tests`
207
213
208
214
#### How to Add a Test
209
215
@@ -288,22 +294,6 @@ Using `$(params.*)` directly in a script creates a security flaw. Tekton perform
288
294
289
295
For more details and guidance on fixing the issue, see the [Tekton recommendations](https://github.com/tektoncd/catalog/blob/main/recommendations.md#dont-use-interpolation-in-scripts-or-string-arguments)
290
296
291
-
### Tekton Task Validation
292
-
293
-
To ensure all Tekton Tasks are well-formed and valid, a `Check Tekton Tasks` workflow is executed on every pull request. This workflow serves as a safeguard to block invalid tasks from being merged, so we don’t risk breaking users.
294
-
295
-
#### If the Check Fails
296
-
297
-
- Open the workflow logs in GitHub Actions
298
-
- Look at the `Apply all Tasks` step
299
-
- The logs will show which Task file failed and the exact error
300
-
301
-
> [!NOTE]
302
-
> The `setup-tektoncd` step may occasionally fail due to GitHub API `rate limits` (see [tektoncd/actions#9](https://github.com/tektoncd/actions/issues/9)).
303
-
> This is a known issue and not related to your changes.
304
-
>
305
-
> The current workaround is to `re-run the workflow`.
0 commit comments