============================
Integration with Forges
============================

Now that you have :doc:`installed CI-tron <installation_and_development>`, you
quite likely would like to expose your test machines (DUTs) on your projects'
GIT forges.

The forge integration has been designed with the following goals in mind:

 * Sane, but partially-or-fully overridable defaults: Allows the same job to
   run on every DUT in the farm, with the possibility to opt-in more control
   only when and where needed.

 * As seamless as possible: running on a CI-tron runner should be as similar
   to running on the default CI runners as possible;

The default boot configuration can be found in
`executor/server/src/valve_gfx_ci/executor/server/templates/boots_db.yml.j2
<https://gitlab.freedesktop.org/gfx-ci/ci-tron/-/blob/main/executor/server/src/valve_gfx_ci/executor/server/templates/boots_db.yml.j2>`_.

.. raw:: html

  <details>
    <summary style="cursor: pointer"><code>executor/server/src/valve_gfx_ci/executor/server/templates/boots_db.yml.j2</code></summary>

.. literalinclude:: ../../executor/server/src/valve_gfx_ci/executor/server/templates/boots_db.yml.j2
   :language: yaml
   :force:

.. raw:: html

  </details><br/>

We currently only support GitLab, but support for more forges is planned and
welcomed.

GitLab
======

To expose your DUTs on a GitLab instance, you will need to add define it in
:ref:`MarsDB`, in the ``gitlab:`` element. Check out :ref:`MarsDB`'s YAML code
block for the details.

.. autoyaml:: .gitlab-ci/dut.yml