---
# CORD API tests using cord-tester, triggered by merge or schedule

- job-template:
    id: triggered-api-test
    name: 'verify_{project}{name-extension}_triggered-api-test'
    description: |
      Triggers an api test in a pipeline post-merge or on a schedule.
      Created by {id} job-template from ci-management/jjb/triggered-api-test.yaml, using pipeline: {pipeline_script}

    triggers:
      - cord-infra-gerrit-trigger-merge:
          gerrit-server-name: '{gerrit-server-name}'
          project-regexp: '^{project}$'
          branch-regexp: '{branch-regexp}'
          file-include-regexp: '{all-files-regexp}'
          dependency-jobs: '{dependency-jobs}'
      - timed: '{timed-trigger}'

    properties:
      - cord-infra-properties:
          build-days-to-keep: '{build-days-to-keep}'
          artifact-num-to-keep: '{artifact-num-to-keep}'

    wrappers:
      - lf-infra-wrappers:
          build-timeout: '60'
          jenkins-ssh-credential: '{jenkins-ssh-credential}'

    parameters:
      - string:
         name: executorNode
         default: 'ubuntu16.04-basebuild-4c-8g'
         description: 'Name of the Jenkins node to run the job on'

      - string:
         name: manifestUrl
         default: '{gerrit-server-url}/{cord-repo-manifest}'
         description: 'URL to the repo manifest'

      - string:
         name: manifestBranch
         default: '$GERRIT_BRANCH'
         description: 'Name of the repo branch to use'

    project-type: pipeline
    concurrent: true

    dsl: !include-raw-escape: pipeline/{pipeline_script}