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
Allow smoke tests to continue when a workspace has runnable metadata for only some published plugins, and surface skipped plugin metadata gaps in workflow comments.
Co-authored-by: Cursor <cursoragent@cursor.com>
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,8 @@ The repository includes an automated smoke testing workflow that verifies plugin
130
130
131
131
**Prerequisites:**
132
132
- PR must touch exactly one workspace
133
-
- Each plugin must have its own metadata file in `workspaces/<modified_workspace>/metadata/`
133
+
- At least one published plugin in the workspace must have runnable metadata in `workspaces/<modified_workspace>/metadata/`
134
+
- Published plugins without runnable metadata are skipped individually
134
135
135
136
**Triggering smoke tests:**
136
137
- After `/publish`: Smoke tests run automatically upon successful publish completion
@@ -139,8 +140,8 @@ The repository includes an automated smoke testing workflow that verifies plugin
139
140
140
141
**Smoke testing workflow steps:**
141
142
1.**Resolve metadata**: Retrieves published OCI references and PR metadata from the `published-exports` artifact
142
-
2.**Prepare test config**: Generates `dynamic-plugins.test.yaml` from plugin metadata (each plugin's `spec.appConfigExamples[0].content` is placed under `pluginConfig`) and copies other configuration files - base (`smoke-tests/app-config.yaml` and workspace-specific `app-config.test.yaml` app-config and `test.env`). The optional `app-config.test.yaml` is for test-only or shared workspace settings that should not appear in the user-facing `appConfigExamples` in metadata.
143
-
3.**Run smoke tests**: Starts RHDH container with layered configuration, installs dynamic plugins from OCI artifacts, and verifies each plugin loads successfully
143
+
2.**Prepare test config**: Generates `dynamic-plugins.test.yaml` from any runnable plugin metadata it finds (each plugin's `spec.appConfigExamples[0].content` is placed under `pluginConfig`) and copies other configuration files - base (`smoke-tests/app-config.yaml` and workspace-specific `app-config.test.yaml` app-config and `test.env`). Published plugins without runnable metadata are skipped; if none are runnable, smoke tests are skipped.
144
+
3.**Run smoke tests**: Starts RHDH container with layered configuration, installs dynamic plugins from OCI artifacts, and verifies each plugin included in the generated config loads successfully
144
145
4.**Report results**: Posts test status as a commit status check and PR comment with pass/fail results and links to the workflow run
Copy file name to clipboardExpand all lines: user-guide/01-getting-started.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -278,7 +278,9 @@ This builds and publishes test OCI artifacts tagged as `pr_<number>__<version>`.
278
278
279
279
After `/publish` completes, smoke tests run automatically if:
280
280
- PR touches exactly one workspace
281
-
- Each plugin has a metadata file
281
+
- At least one published plugin has runnable metadata
282
+
283
+
Published plugins without runnable metadata are skipped individually. Smoke tests are skipped only when no published plugin in the workspace can produce runnable metadata, or when plugin config references environment variables and the workspace `smoke-tests/test.env` file is missing. If the file exists but required variables are missing from it, the workflow fails instead of skipping.
0 commit comments