Once dependencies are solved, patchtest should be deployed on a server so it starts monitoring community patches. README file has all instructions for setting up the server with patchtest and patchtest-oe. Because patchtest execution is expected to be an automated process, the section 'Host installation & guest execution' must be used this time. Once this step is done, a new cronjob must be scheduled (the frequency needs to be defined) calling the script scripts/pt-cronjob with correct parameter.
Michael, Currently tool is running locally (not in a YP server) and using some beta users. I let you know when the tool is ready to be deployed.
*** Bug 10620 has been marked as a duplicate of this bug. ***
Michael, patchtest can be now be deployed at one of the LF servers. Full documentation is located at patchtest repo, under the doc folder.
Michael, last weeks I worked on some scripts and documentation that easier patchtest deployment on a server (all this work under the patchtest repo, so please pull). Jose and myself will be working on resolving 10877 as soon as possible but in the mean time you may start with this one **except** running the cronjob (I am running the latter in my laptop and just sending to beta users). All documentation is now in just one file (usage.adoc) so follow that one.
Server deployment complete. Thank you Leonardo for the excellent hand-off.
(In reply to comment #6) > Server deployment complete. Thank you Leonardo for the excellent hand-off. Michael, can you check the cron is running correctly? there are some untested series on patchwork (series > 5107 have been untested)
It was stuck at a sudo prompt. It's passing that now.
Michael, seems that just one run of the cronjob executed, but currently it is not working. Reopening the bug so we can fix it today.
The network interface creation was failing due to requiretty in the default sudo settings. I've disabled this for the patchtest user. Cron runs appear to be working.
Cron is working as expected.