runbot

mirror of https://github.com/odoo/runbot.git synced 2025-03-19 01:15:48 +07:00

History

Xavier Morel af8c62e4ad [FIX] runbot_merge: better handle targets being branch-protected If a staging covers multiple repositories and there's a fast-forward issue on any but the first repo/target, runbot_merge attempted to revert the commits it had fast-forwarded on the previous repos. This doesn't work when branch-protection is active, unless runbot_merge is a repository administrator (and branch protection is not configured to apply to those): reverting is done by push-forcing the original head back onto the ref, which branch-protection unconditionally precludes. This commit does not entirely fix the race condition (it does not look like github provides any way to do that), but it should significantly reduce the race-condition window as it performs a semi-wet run of the fast-forward process on the tmp branches before actually updating the targets. That way the only remaining breakage should be when somebody pushes on repositories 1.. between the test-FF on tmp branches and the actual fast forward. While at it, updated the github API thing to always dump the JSON body on an error response, if the content-type is json.		2018-10-10 10:50:21 +02:00
..
fake_github	[FIX] runbot_merge: better handle targets being branch-protected	2018-10-10 10:50:21 +02:00
conftest.py	[IMP] runbot_merge: pluginify github mock	2018-09-03 13:16:36 +02:00
local.py	Better reporting of staging state	2018-10-01 10:21:32 +02:00
README.rst	[IMP] runbot_merge: test readme & remove leftover pass	2018-09-03 13:16:36 +02:00
remote.py	[FIX] runbot_merge: better handle targets being branch-protected	2018-10-10 10:50:21 +02:00
test_basic.py	[FIX] runbot_merge: better handle targets being branch-protected	2018-10-10 10:50:21 +02:00
test_multirepo.py	[FIX] runbot_merge: better handle targets being branch-protected	2018-10-10 10:50:21 +02:00
test_utils.py	[FIX] runbot_merge: ensure all staging branches are built/tested	2018-09-11 10:21:24 +02:00

README.rst

Execute this test suite using pytest.

The default mode is to run tests locally using a mock github.com.

See the docstring of remote.py for instructions to run against github "actual"
(including remote-specific options) and the end of this file for a sample.

Shared properties running tests, regardless of the github implementation:

* test should be run from the root of the runbot repository providing the
  name of this module aka ``pytest runbot_merge`` or
  ``python -mpytest runbot_merge``
* a database name to use must be provided using ``--db``, the database should
  not exist beforehand
* the addons path must be specified using ``--addons-path``, both "runbot" and
  the standard addons (odoo/addons) must be provided explicitly

See pytest's documentation for other options, I would recommend ``-rXs``,
``-v`` and ``--showlocals``.

When running "remote" tests as they take a very long time (hours) ``-x``
(aka ``--maxfail=1``) and ``--ff`` (run previously failed first) is also
recommended unless e.g. you run the tests overnight.

``pytest.ini`` sample
---------------------

.. code:: ini

    [github]
    owner = test-org
    token = aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

    [role_reviewer]
    name = Dick Bong
    user = loginb
    token = bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb

    [role_self_reviewer]
    name = Fanny Chmelar
    user = loginc
    token = cccccccccccccccccccccccccccccccccccccccc

    [role_other]
    name = Harry Baals
    user = logind
    token = dddddddddddddddddddddddddddddddddddddddd