On 03/09/16 14:02, Dominic Cleal wrote: > 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.
Two further points: 1. PR tests will no longer be suspended when test_develop is failing, so please expect to rebase or re-test PRs after an issue is fixed on develop instead of relying on it to automatically clear. I don't think this original behaviour is possible with the plugin. 2. Commenting on an existing PR that was tested on the old system for the first time will cause the new PR tests to run too, so expect to see a few more builds over the next few days. You'll see both new and old statuses reported on a PR commit if this happens, simply ignore the old one, it's nothing to worry about. -- 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.
