Skip to content

fix: update GitHub Actions workflow for Java example#505

Draft
SimiHunjan wants to merge 10 commits intomainfrom
test-standard-runner
Draft

fix: update GitHub Actions workflow for Java example#505
SimiHunjan wants to merge 10 commits intomainfrom
test-standard-runner

Conversation

@SimiHunjan
Copy link
Copy Markdown
Contributor

Updated the GitHub Actions workflow to use Ubuntu as the runner and modified environment variables for the mirror node. Replaced Node.js setup with Homebrew installation and updated the Solo CLI installation method.

Description:

Related issue(s):

Fixes #

Notes for reviewer:

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

Updated the GitHub Actions workflow to use Ubuntu as the runner and modified environment variables for the mirror node. Replaced Node.js setup with Homebrew installation and updated the Solo CLI installation method.

Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
@mintlify
Copy link
Copy Markdown
Contributor

mintlify bot commented Apr 15, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
hedera-docs 🟢 Ready View Preview Apr 15, 2026, 7:38 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@SimiHunjan SimiHunjan self-assigned this Apr 15, 2026
@SimiHunjan SimiHunjan changed the title Update GitHub Actions workflow for Java example fix: update GitHub Actions workflow for Java example Apr 15, 2026
Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
@theekrystallee
Copy link
Copy Markdown
Member

thanks for the PR @SimiHunjan. are we not using the hashgraph runner anymore?

@andrewb1269

@andrewb1269
Copy link
Copy Markdown
Contributor

@theekrystallee we certainly should be using the hashgraph hosted runners, not the generic Ubuntu latest runner.

update workflow

Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
Updated the mirror URL for the Java examples runner.

Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
Removed the step to get all service ports from the workflow.

Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
Updated the verification script to check transaction count instead of node count.

Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>
@SimiHunjan
Copy link
Copy Markdown
Contributor Author

This was test to validate that the standard GitHub runners can run Solo without any issues as before the memory footprint was to high and failed on standard GitHub runners.

Is it really required to use self hosted runners if the standard GitHub runners serves the purpose? I can switch it back, but was planning to leave it here as a case for Solo working on a standard GitHub runner. @andrewb1269

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.

3 participants