-
Notifications
You must be signed in to change notification settings - Fork 898
[CI] Rebuild simple-game-server for each e2e test? #4329
Copy link
Copy link
Closed
Labels
area/build-toolsDevelopment tooling. I.e. pretty much everything in the `build` directory.Development tooling. I.e. pretty much everything in the `build` directory.area/testsUnit tests, e2e tests, anything to make sure things don't breakUnit tests, e2e tests, anything to make sure things don't break
Description
Testing new version of the simple-game-server is super manual and annoying.
I had a thought today -- why don't we rebuild simple-game-server on each build and put a hash on it, and put it in one of the repositories that cleans itself up?
We could probably use the commit as the hash, and cache against it for rebuilds.
Then we tell the e2e test "use this build", which I'm 97% sure we have overrides for in the make commands.
I can't think of a huge downside tbh.
Thoughts?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/build-toolsDevelopment tooling. I.e. pretty much everything in the `build` directory.Development tooling. I.e. pretty much everything in the `build` directory.area/testsUnit tests, e2e tests, anything to make sure things don't breakUnit tests, e2e tests, anything to make sure things don't break