Replies: 2 comments 4 replies
-
I think it does have value. On every push might be too much as it's a longer running test. Putting it as a pre-release might be a concern as it could fail the release at the last minute. Perhaps we can have it as a nightly/weekly job instead? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I just noticed your workflow doesn't run the tests. We'd probably want to run those as well to catch Windows specific runtime errors and making it run less often would allow us to. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
G'day folks,
With the mirror node now building on Windows, I'm wondering if an action or workflow could be added to keep an eye on things?
I appreciate Ubuntu is the preferred environment, and would envisage most Windows developers using docker and WSL2 for deployments, however, having the mirror node reliably build on Windows should be useful as Hedera's decentralization continues and interest grows.
By way of example, here is the result of building on Windows Server 2019 using this workflow.
A build takes ~5-6 minutes once the maven packages are cached, but not sure if it would be needed on each push; running on (pre)release might suffice?
Beta Was this translation helpful? Give feedback.
All reactions