I've changed the PR test jobs in Jenkins for the main Foreman repo (theforeman/foreman) to try and improve performance. You'll see that PRs now receive "foreman", "upgrade" and "katello" test statuses, replacing "default".
The old [test] phrase changes to the following commands: 1. "[test foreman]" or "[test upgrade]" to re-test a PR that has failed tests (as always, use this sparingly please) 2. "ok to test" to run tests for an unknown user, if the patch is not malicious (the plugin will unfortunately add three comments to ask, one per test) 3. "add to PR whitelist" to always run tests from a trusted user If you forget, they're on the wiki at http://projects.theforeman.org/projects/foreman/wiki/Jenkins#Quick-reference-for-maintainers. Aside from these cosmetic changes, the tests should work identically to before. Please note that plugins and other repo PR tests remain completely unchanged for now, I'll look at migrating those if this works well. This uses the GHPRB Jenkins plugin, replacing our test-pull-requests script. It has a few advantages, such as running the jobs separately to reduce the number of slave slots used, and aborting running jobs when a PR is updated. I hope it will improve the general throughput of PR tests, particularly under very high load by ensuring more slave slots are actively running tests. Info is also on the wiki: http://projects.theforeman.org/projects/foreman/wiki/Jenkins#Pull-request-testing Please reply if there are any new issues with the PR tests. -- Dominic Cleal domi...@cleal.org -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
