Skip to content

Edburns/dd 2855288 add smoke test to build and test #23

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
edburns merged 5 commits into from
Mar 25, 2026
Merged

Edburns/dd 2855288 add smoke test to build and test #23

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
00a8c7e
Add smoke test agentic workflow
edburns Mar 25, 2026
f067cb9
On branch edburns/dd-2855288-add-smoke-test-to-build-and-test
edburns Mar 25, 2026
922af2f
Add smoke test agentic workflow
edburns Mar 25, 2026
f26ed4d
Apply suggestion from @Copilot
edburns Mar 25, 2026
200fe54
Apply suggestion from @Copilot
edburns Mar 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Apply suggestion from @Copilot 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  • Loading branch information
@edburns
edburns and Copilot authored Mar 25, 2026
commit f26ed4d2ed67dfa36036cce55952ecff3c821b2e
6 changes: 3 additions & 3 deletions .github/workflows/run-smoke-test.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,11 +74,11 @@ This must complete with `BUILD SUCCESS`. If it fails, report failure and stop.

### Step 2 — Execute the smoke test prompt

Read the file `src/test/prompts/PROMPT-smoke-test.md` and follow its instructions exactly.
Read the file `src/test/prompts/PROMPT-smoke-test.md` and follow its instructions, with the override described below.

**Critical override:** Because the SDK was already built and installed into the local Maven repository in Step 1, the snapshot artifact is already available locally. Maven resolves local repository artifacts before remote ones, so the snapshot repository configuration in the prompt will still work correctly — it will just find the artifact locally instead of downloading it.
**Critical override:** The goal of this workflow is to validate the SDK snapshot you just built and installed locally in Step 1, not any newer SNAPSHOT that might exist in a remote repository. To ensure Maven does not download a newer timestamped SNAPSHOT, you must run the smoke-test Maven build in offline mode and without `-U`, so that it uses the locally installed artifact.

Follow every step in the prompt: create the `smoke-test/` directory, create `pom.xml` and the Java source file exactly as specified, build with `mvn -U clean package`, run with `java -jar`, and verify the exit code.
Follow every step in the prompt: create the `smoke-test/` directory, create `pom.xml` and the Java source file exactly as specified, then **when the prompt instructs you to run `mvn -U clean package`, instead run** `mvn -o clean package` (no `-U`), run with `java -jar`, and verify the exit code.

### Step 3 — Report result

Expand Down