Skip to content

[CFX-6647] windows smoke tests for exercising dr self completion install#607

Draft
ajalon1 wants to merge 6 commits into
datarobot-oss:mainfrom
ajalon1:aj/CFX-6647-remote-signed-ps1
Draft

[CFX-6647] windows smoke tests for exercising dr self completion install#607
ajalon1 wants to merge 6 commits into
datarobot-oss:mainfrom
ajalon1:aj/CFX-6647-remote-signed-ps1

Conversation

@ajalon1

@ajalon1 ajalon1 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

RATIONALE

Realized that we don't have smoke tests for dr self completion install, only for dr self completion.

CHANGES

Add to Windows smoke tests PS1 two testing scenarios:

  • dr self completion install when execution policy is restricted, as when we have a fresh Windows install
  • dr self completion install when execution policy is permissive

Document some of the methods.

oof, writing PS1 scripts.

PR Automation

Comment-Commands: Trigger CI by commenting on the PR:

  • /trigger-smoke-test or /trigger-test-smoke - Run smoke tests
  • /trigger-install-test or /trigger-test-install - Run installation tests

Labels: Apply labels to trigger workflows:

  • run-smoke-tests or go - Run smoke tests on demand (only works for non-forked PRs)

Important

For Forked PRs: The run-smoke-tests label won't work. A required Smoke Tests check will block merge until a maintainer acts:

  • A maintainer uses /approve-smoke-tests to run smoke tests (results will set the check)
  • A maintainer uses /skip-smoke-tests to bypass the check without running tests

Please comment requesting a maintainer review if you need smoke tests to run.

ajalon1 and others added 6 commits June 25, 2026 16:46
Get-DRCompletionProfilePath and Test-DRCompletionProfile were each called
from exactly one site. Inline them into Test-DRCompletionInstallWithExecutionPolicy
to co-locate the logic with its only consumer.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
@ajalon1

ajalon1 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor Author

/approve-smoke-tests

@github-actions

Copy link
Copy Markdown
Contributor

🔐 Fork PR smoke tests triggered by @ajalon1

⚠️ Security Notice: This will run tests with access to repository secrets.

What happens next:

  1. Security scans will run automatically (Trivy, gosec)
  2. If security scans pass, smoke tests will run
  3. Results will be posted as PR comments

⚠️ Important: Review the PR code carefully before approving!

@github-actions

Copy link
Copy Markdown
Contributor

🔐 Fork smoke tests started by maintainer

⏳ Security scans passed. Running smoke tests...

Commit: 4b7625c0995e107cc551459b6db1c5cd5698c7ab
View run

@github-actions

Copy link
Copy Markdown
Contributor

Some smoke tests failed. (Fork PR)

✅ Security Scan: success
✅ Linux: success
❌ Windows: failure

View run details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant