Klever

One more welcome feature of Klever.

Supported since 32bc780.

To verify external Linux kernel modules one needs to place their archive like other job files and specify an archive path and target modules in a job. For instance:

• to verify all external modules:
  

  "Linux kernel": {
    "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
    "modules": ["all"]
  }
  

• to verify all external modules from directory S and U-double_mutex_lock.ko:
  

  "Linux kernel": {
    "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
    "modules": ["S", "U-double_mutex_lock.ko"]
  }
  

• to verify all external modules from directory S:
  

  "Linux kernel": {
    "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
    "modules": ["S"]
  }
  

• to verify U-double_mutex_lock.ko:
  

  "Linux kernel": {
    "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
    "modules": ["U-double_mutex_lock.ko"]
  }
  

• to verify S/S-mutex_lock.ko:
  

  "Linux kernel": {
    "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
    "modules": ["S/S-mutex_lock.ko"]
  }
  

At the moment just one archive with external Linux kernel modules can be specified per a job (sub-job). This is the most flexible solution since we can easily configure a remaining part of a job (sub-job) independently for each archive.