Skip to content

PR testing

Dominic Hofer edited this page Nov 17, 2021 · 1 revision

To automatically test a PR you can use the trigger phrase

launch jenkins ...

followed by a space separated list of predefined commands and the optional flag --upstream, or a raw spack command.

Examples:

launch jenkins atlas cuda zlib_ng (No upstream will be used. Predefined commands "atlas, cuda, zlib_ng" will be triggered.)

launch jenkins --upstream all (Upstream will be used. Predefined command "all" will be triggered.)

launch jenkins spack installcosmo cosmo@master%pgi cosmo_target=gpu +cppdycore (Raw spack command will be executed.)

Using predefined command will trigger a set of packages and packages depending on those packages. This total set of packages is mapped to a set of use cases which then will be tested. (See test_spack.py)

Supported commands

Others:

  • all (tests all use cases)
  • a raw spack command

Based on a package name:

  • atlas
  • atlas_utilities
  • claw
  • cosmo
  • cosmo-dycore
  • cosmo-eccodes-definitions
  • cosmogrib-api
  • cosmo-grib-api-definitions
  • cuda
  • dawn
  • dawn4py
  • dusk
  • dyicon_benchmarks
  • ecbuild
  • eccodes
  • eckit
  • gridtools
  • icon
  • icondusk-e2e
  • icontools
  • int2lm
  • libgrib1
  • mpich
  • oasis
  • omnicompiler
  • omni-xmod-pool
  • openmpi
  • serialbox
  • xcodeml-tools
  • zlib_ng
Clone this wiki locally