Good. We should use Jenkins to automate as much testing as possible, e.g.:
- end-to-end test (compile code, create project, add apps/jobs, run client, process job, make sure that it validates and gets credit) - test Win/Mac installers: make sure they succeed, and that the resulting client works. - test PHP code (I'm not sure how to do this). On the BOINC workshop wiki page, I suggested this as a hackfest topic (i.e. developing some of the above tests) -- David On 18-Sep-2014 7:38 PM, Rom Walton wrote:
David, Well, Jenkins is setup and working. We will probably need to monkey with things in the future, if we include different types of build nodes for cross-compiling and the like. You can see changes to the Trac timeline: http://boinc.berkeley.edu/trac/timeline?from=09%2F18%2F14&daysback=90&au thors=&build=on&changeset=on&milestone=on&ticket=on&wiki=on&update=Updat e Jenkins will also send email to [email protected] when a build fails.
_______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
