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
cli: test and publish Debian package #452
Comments
Making good progress. We've just merged ooni/probe-cli#117, which creates the package and publishes it on bintray. Now I am going to add this new package to the e2etesting suite such that it runs every day. |
While there relax the testing policy and test three times per day, which is enough given we've flipped the API now. This counts as progress for ooni/backend#452 Future commits will further improve the tests we're running here.
* feat: add e2etest for debian package While there relax the testing policy and test three times per day, which is enough given we've flipped the API now. This counts as progress for ooni/backend#452 Future commits will further improve the tests we're running here. * fix: remember to onboard * fix: install the right package name * fix: use correct run command
With ooni/e2etesting#27 merged, we periodically ensure the debian package is WAI. |
We've made good progress with @FedericoCeratto in Sprint 26. There is more work to do in Sprint 27. |
We have further improved the package with @FedericoCeratto here: ooni/probe-cli#162. We now have a package that can be installed and can in the background. The package is triggered by a timer that fires off daily. The user needs to accept data collection while the package is being installed, otherwise there's not running in background. |
I suppose we can call this done! 🎉🎉🎉 |
Upload a package in Debian contrib/non-free that:
When asking for updates, send basic info about the host so we can deploy updates only where supported.
Reuse the same update protocol for other OSes?
The text was updated successfully, but these errors were encountered: