TrustedFirmware Git Browser
Code Review Sign In
review.trustedfirmware.org / next / ci / ci-yadp-builder / 1a58e364d6b901811a81cd10b2c1d878cab5668b
commit1a58e364d6b901811a81cd10b2c1d878cab5668b[log] [tgz]
authorPaul Sokolovsky <paul.sokolovsky@linaro.org>Thu Jul 28 20:42:46 2022 +0300
committerPaul Sokolovsky <paul.sokolovsky@linaro.org>Thu Jul 28 20:42:46 2022 +0300
tree0d4b7275efadd8b0b6386d01b36040dd264af0c2
parentd12cdd4c2b4f3541c1368d46251938eea2dbe0a8 [diff]
pfalcon_templates.yml: Use production docker image name and label

Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
Change-Id: Iefbd3af29c6a8dad4ad42938ea74775e57742531
1 file changed
tree: 0d4b7275efadd8b0b6386d01b36040dd264af0c2
  1. templates/
  2. .gitreview
  3. docker_ssh_buildslave.yml
  4. docker_templates_amd64.yml
  5. hosts
  6. mbed_tls_host_docker_vol.yml
  7. pfalcon_templates.yml
  8. README.md
  9. yadp_builder.py
  10. yadp_builder_v2.py
README.md

Yet Another Docker Plugin config builder

Yet Another Docker Plugin (YADP) is extremely hard to manage, when running multiple slaves with multiple images. Due to the way Jenkins displays the configuration page. YADP provides a groovy script which builds a JSON array to populate the configuration in Jenkins.

This script uses YAML and Jinja2 to generate a java JSONARRAY to build the configuration, using a !include constructor in the YAML file, allowing the ability to template up docker_images, since many of our slaves run the same image, it lessens repetition.

Features

  1. Ability to !include inside YAML to lessen duplication
  2. Ability to include multiple YAML files with !include [file1.yml, file2.yml]
  3. Ability to include SSH settings via using launch_method:" along with ssh: or jnlp:

Usage

####hosts

- host1:
  cloud_name: host1.example.org
  docker-url: tcp://0.0.0.0:2375
  docker_templates: !include external_template_file.yml

- host2:
  cloud_name: host2.example.org
  docker-url: tcp://0.0.0.1:2375
  docker_templates:
    - xenial-amd64:
      docker_image_name: 'ubuntu:latest'
      max_instances: '1'
      labels: 'docker-ubuntu'
      launch_method: ssh
      ssh:
        launch_ssh_credentials_id: 'random-id'
        launch_ssh_port: '22'

- host3
  cloud_name: host3.example.org
  docker-url: tcp://0.0.0.0:2375
  docker_templates:
    !include [external_template_file.yml, external_template_file_2.yml]

Limitations

Due to the nature of YAML and populating the Java JSONARRAY, its important that YAML is phased correctly.

Most of the limitations surround docker_templates.

A list of limitations and pending improvements.

  1. Do not mix !include and templates under docker_templates.

Example of broken approach:

  • host1: cloud_name: host1.example.org docker-url: tcp://0.0.0.0:2375 docker_templates: !include external_template_file.yml
    • xenial-amd64: docker_image_name: 'ubuntu:latest' max_instances: '1' labels: 'docker-ubuntu'
  1. Do not add spaces under the image cloud_name, the must fall inline with the image name

Example of broken approach:

  • xenial-amd64: docker_image_name: 'ubuntu:latest' max_instances: '1' labels: 'docker-ubuntu'
  1. Docker labels could be "host" specific. If you are including a template file, the template has no link to the host, so its not possible to do "host based labels". Instead just create another template file with custom settings and include that file.