Project

General

Profile

Actions

Bug #18264

closed

[CI] simplify the way we run the CWL tests

Added by Ward Vandewege over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Story points:
-
Release relationship:
Auto

Description

We currently run the CWL tests on our test clusters by launching a custom script on the main jenkins server which copies and runs a custom script to the shell node of the cluster. This is convoluted and error prone. Make some changes:

  • instead of running with -j1, increase the parallelism to whatever the target cluster can handle (the bottleneck is the machine that runs a-c-r !)
  • instead of relying on a shell node, just start a jenkins satellite with appropriate Arvados credentials for the target cluster and run the test suite that way
  • instead of having one CI job for the upstream CWL test suite and our Arvados CWL tests, make those 2 jobs and run them in parallel (if the target cluster can handle that)
  • if possible, instead of one (a pair of) CI jobs for each cluster, make a parameterized job that is launched with the appropriate parameters in the build pipeline for each cluster

Subtasks 1 (0 open1 closed)

Task #18271: reviewResolvedPeter Amstutz10/26/2021Actions

Related issues

Blocked by Arvados - Bug #18238: CWL integration test failingResolvedPeter AmstutzActions
Actions

Also available in: Atom PDF