Commit 6a6ee6f4 authored by Neil Williams's avatar Neil Williams
Browse files

Handle change to git.linaro.org frontend

gitweb urls need to be changed to cgit references.

Change-Id: I1a24dc484c0452bba94c17e26238c722d9ec909d
parent 267d2230
......@@ -187,7 +187,7 @@ the same definition:
Inline test definition example
==============================
https://git.linaro.org/lava/lava-dispatcher.git/blob/HEAD:/lava_dispatcher/pipeline/test/sample_jobs/kvm-inline.yaml
https://git.linaro.org/lava/lava-dispatcher.git/tree/lava_dispatcher/pipeline/test/sample_jobs/kvm-inline.yaml
.. code-block:: yaml
......
......@@ -394,7 +394,7 @@ unit tests::
The list of python3 dependencies needed for the pipeline unit tests is
maintained as part of the functional tests:
https://git.linaro.org/lava-team/refactoring.git/blob/HEAD:/functional/dispatcher-pipeline-python3.yaml
https://git.linaro.org/lava-team/refactoring.git/tree/functional/dispatcher-pipeline-python3.yaml
From time to time, reviews may add more python dependencies - check on the
:ref:`mailing_lists` if your tests start to fail after rebasing on current
......
......@@ -286,7 +286,7 @@ device looks like:
{% set power_off_command = '/usr/local/lab-scripts/snmp_pdu_control --hostname pdu15 --command off --port 11' %}
{% set power_on_command = '/usr/local/lab-scripts/snmp_pdu_control --hostname pdu15 --command on --port 11' %}
https://git.linaro.org/lava/lava-lab.git/blob/HEAD:/staging.validation.linaro.org/lava/pipeline/devices/staging-black01.jinja2
https://git.linaro.org/lava/lava-lab.git/tree/staging.validation.linaro.org/lava/pipeline/devices/staging-black01.jinja2
.. note:: It is recommended to keep the device dictionary jinja files under
version control. The templates are configuration files, so if you modify the
......
......@@ -102,7 +102,7 @@ the following:
The first job mentioned above uses a more complex test definition:
https://git.linaro.org/qa/test-definitions.git/blob/HEAD:/ubuntu/smoke-tests-basic.yaml
https://git.linaro.org/qa/test-definitions.git/tree/ubuntu/smoke-tests-basic.yaml
The metadata in a test definition is for the maintenance of that test
definition and covers details like the maintainer, the kinds of devices which
......
......@@ -88,9 +88,9 @@ definitions, some optional:
* ``IRC_SERVER``: (optional) The IRC network to use for notifications, used if
IRC_USER is also set. This defaults to ``irc.freenode.net``
.. _hacking-session-debian.yaml: https://git.linaro.org/lava-team/hacking-session.git/blob_plain/HEAD:/hacking-session-debian.yaml
.. _hacking-session-fedora.yaml: https://git.linaro.org/lava-team/hacking-session.git/blob_plain/HEAD:/hacking-session-fedora.yaml
.. _hacking-session-oe.yaml: https://git.linaro.org/lava-team/hacking-session.git/blob_plain/HEAD:/hacking-session-oe.yaml
.. _hacking-session-debian.yaml: https://git.linaro.org/lava-team/hacking-session.git/tree/hacking-session-debian.yaml
.. _hacking-session-fedora.yaml: https://git.linaro.org/lava-team/hacking-session.git/tree/hacking-session-fedora.yaml
.. _hacking-session-oe.yaml: https://git.linaro.org/lava-team/hacking-session.git/tree/hacking-session-oe.yaml
.. _example: https://staging.validation.linaro.org/scheduler/job/138105/definition
Starting a Hacking Session
......
......@@ -418,8 +418,8 @@ Parameters used in the test definition YAML can be controlled from the YAML job
file. See the following YAML test definition to get an understanding of how it
works.
* YAML test definition - https://git.linaro.org/lava-team/lava-functional-tests.git/blob/HEAD:/lava-test-shell/params/params.yaml
* YAML job submission - https://git.linaro.org/lava-team/refactoring.git/blob/HEAD:/kvm-params.yaml
* YAML test definition - https://git.linaro.org/lava-team/lava-functional-tests.git/tree/lava-test-shell/params/params.yaml
* YAML job submission - https://git.linaro.org/lava-team/refactoring.git/tree/kvm-params.yaml
Install Steps
=============
......
......@@ -56,12 +56,12 @@ Don't worry about running this example yourself at this stage. The files
themselves may be useful for reference. The device YAML file comes from the
lava-dispatcher unit tests:
https://git.linaro.org/lava/lava-dispatcher.git/blob/HEAD:/lava_dispatcher/pipeline/devices/bbb-01.yaml
https://git.linaro.org/lava/lava-dispatcher.git/tree/lava_dispatcher/pipeline/devices/bbb-01.yaml
The job submission YAML used in the example comes from the lava-team
refactoring repository of functional tests:
https://git.linaro.org/lava-team/refactoring.git/blob/HEAD:/bbb-uboot-ramdisk.yaml
https://git.linaro.org/lava-team/refactoring.git/tree/bbb-uboot-ramdisk.yaml
.. code-block:: yaml
......@@ -550,9 +550,9 @@ commands.
The first point of reference with a new template is the ``lava-server``
`base.jinja2
<https://git.linaro.org/lava/lava-server.git/blob/HEAD:/lava_scheduler_app/tests/device-types/base.jinja2>`_
<https://git.linaro.org/lava/lava-server.git/tree/lava_scheduler_app/tests/device-types/base.jinja2>`_
template and existing examples (e.g. `beaglebone-black
<https://git.linaro.org/lava/lava-server.git/blob/HEAD:/lava_scheduler_app/tests/device-types/beaglebone-black.jinja2>`_)
<https://git.linaro.org/lava/lava-server.git/tree/lava_scheduler_app/tests/device-types/beaglebone-black.jinja2>`_)
- templates live on the server, are populated with data from the database and
the resulting YAML is sent to the dispatcher.
......@@ -668,7 +668,7 @@ Creating a device dictionary for the device
===========================================
Examples of exported device dictionaries exist in the ``lava-server`` `codebase
<https://git.linaro.org/lava/lava-server.git/blob/HEAD:/lava_scheduler_app/tests/bbb-01.yaml>`_
<https://git.linaro.org/lava/lava-server.git/tree/lava_scheduler_app/tests/bbb-01.yaml>`_
for unit test support. The dictionary extends the new template and provides the
device-specific values.
......
......@@ -271,7 +271,7 @@ final operation.
Complete Multinode test definition
==================================
https://git.linaro.org/lava-team/refactoring.git/blob_plain/HEAD:/bbb-ssh-guest.yaml
https://git.linaro.org/lava-team/refactoring.git/plain/bbb-ssh-guest.yaml
.. code-block:: yaml
......
......@@ -148,7 +148,7 @@ Notes
correctly, resulting in the secondary connection jobs being incomplete. A
final test definition of smoke tests or other quick checks could be useful.
https://git.linaro.org/lava-team/refactoring.git/blob/HEAD:/mustang-ssh-guest.yaml
https://git.linaro.org/lava-team/refactoring.git/tree/mustang-ssh-guest.yaml
.. code-block:: yaml
......
......@@ -33,7 +33,7 @@ Job definitions in version control
It is normally recommended to also store your test job YAML files in the
repository. This helps others who may want to use your test definitions.::
https://git.linaro.org/lava-team/refactoring.git/blob_plain/HEAD:/panda-multinode.yaml
https://git.linaro.org/lava-team/refactoring.git/tree/panda-multinode.yaml
There are numerous test repositories in use daily in Linaro that may be good
examples for you, including:
......
......@@ -261,15 +261,15 @@ directory at the end of the script.
Example of a custom script wrapping the output:
https://git.linaro.org/lava-team/refactoring.git/blob/HEAD:/functional/unittests.sh
https://git.linaro.org/lava-team/refactoring.git/tree/functional/unittests.sh
The script is simply called directly from the test shell definition:
https://git.linaro.org/lava-team/refactoring.git/blob/HEAD:/functional/server-pipeline-unit-tests.yaml
https://git.linaro.org/lava-team/refactoring.git/tree/functional/server-pipeline-unit-tests.yaml
Example V2 job using this support:
https://git.linaro.org/lava-team/refactoring.git/blob/HEAD:/functional/qemu-server-pipeline.yaml
https://git.linaro.org/lava-team/refactoring.git/tree/functional/qemu-server-pipeline.yaml
.. _interpreters_scripts:
......
......@@ -147,7 +147,7 @@ BRANDING_URL = 'http://www.linaro.org'
BRANDING_HEIGHT = "BRANDING_HEIGHT", 22
BRANDING_WIDTH = "BRANDING_WIDTH", 22
BRANDING_BUG_URL = "https://bugs.linaro.org/enter_bug.cgi?product=LAVA%20Framework"
BRANDING_SOURCE_URL = "https://git.linaro.org/gitweb?s=lava%2Flava"
BRANDING_SOURCE_URL = "https://git.linaro.org/lava"
# Logging
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment