Staging instance, all changes can be removed at any time

Skip to content

Add a job running swh-mirror tests

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:
org.softwareheritage.mirror.monitoring=true
org.softwareheritage.mirror.volumes.storage-db=true
org.softwareheritage.mirror.volumes.web-db=true
org.softwareheritage.mirror.volumes.objstorage=true
org.softwareheritage.mirror.volumes.redis=true

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 swh/infra/swh-mirror!5 (closed) to work.


Migrated from D8671 (view on Phabricator)

Merge request reports

Loading