Skip to content
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.

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

Staging and Tests against Dojos #580

Open
ConnorNelson opened this issue Sep 26, 2024 · 0 comments
Open

Staging and Tests against Dojos #580

ConnorNelson opened this issue Sep 26, 2024 · 0 comments

Comments

@ConnorNelson
Copy link
Member

No seriously.

This affects our development speed and quality of our platform significantly. As things currently stand, this might even be more important than ripping out our NFS bottleneck for multi-node (and if not, it is just behind that).

I should be able to know if changes to this repository will affect the solvability of dojos.

We need an interface for dojos to declare testcases. This will need a mechanism for those testcases to be private, because probably most of the tests will be "does my solution script work?". And then we need infrastructure that runs those testscases against production.

  • Phase 1: Button that can be pressed to run CI
  • Phase 2: Run all the tests every night / after every update
  • Phase 3: Staging server to get a before-it-goes-live understanding

Picture this ultra fancy system:

  • Push to master
  • That immediately deploys to https://staging.pwn.college/
  • Testcases run
  • Drop some poor unsuspecting users randomly into that instance and see if anyone complains (the real testcase)
  • Push to stable branch after 24h without issue
  • Deploy stable branch to https://pwn.college/

Make it all automatic and delete @zardus's keys. Bumo.

Seriously, we should at least get a system that supports phase 1.

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

No branches or pull requests

1 participant