Page MenuHomeSoftware Heritage

Add a job running swh-mirror tests

Authored by lunar on Oct 13 2022, 11:13 AM.



swh-mirror tests are quite involved as they deploy a replicated Software
Heritage Archive in the form of a Docker swarm.

This new swh-mirror/run-tests job assumes that Jenkins running has
access to a Docker engine. It needs:

  1. to be able to build images;
  2. to be configured as part of a swarm;
  3. to have at least one node with the following labels:

The pipeline will first create up-to-date Docker images used by the
swarm (using Jenkins host) and then run pytest in a Docker container
using swh-jenkins/tox.

As it depends on network resources, the test can drag for quite long.
The timeout is currently set at one hour. In most cases the pipeline
will be done in 15-20 minutes.

Care is taken both in the test code and within the Jenkins pipeline to
remove resources related to the Docker swarm (stack, containers, configs
and volumes) on teardown.

The job will need the changes proposed as D8634 to work.

Diff Detail

rCJSWH Jenkins jobs
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

Here is screenshot of the resource monitor on my system while running the test:

anlambert added inline comments.

Found the issue, as explained by the raised exception when running Jenkins jib builder: jinja2.exceptions.TemplateNotFound: includes/agent-docker.groovy.j2, the template file could not be found. Jenkins job builder includes files relative to the yaml file describing the job so the correct way to include the docker agent here is the following:*

{% filter indent(width=8) %}
  {%- include 'templates/includes/agent-docker.groovy.j2' -%}
{% endfilter %}

Use the template appropriately to run the Docker agent

lunar added inline comments.

I should have thought about it but this was really not obvious. Thank you!

Screenshot of resources usage while test runs on my laptop:

This revision is now accepted and ready to land.Nov 7 2022, 1:41 PM
This revision was automatically updated to reflect the committed changes.