- <td><b>Jenkins Label</b><br/> dynamic_merge</td>
- <td><b>Minion Template name</b><br/> centos7-builder</td>
- <td><b>Vagrant Definition</b><br/> releng/builder/vagrant/basic-builder</td>
- <td><b>Spinup Script</b><br/> releng/builder/jenkins-scripts/builder.sh</td>
- </tr>
- <tr>
- <td colspan="4">
- See dynamic_verify (same image on the back side). This is the label that
- is used for all basic -merge and -integration- builds for projects.
- </td>
- </tr>
-
- <tr class="warning">
- <td><b>Jenkins Label</b><br/> matrix_master</td>
- <td><b>Minion Template name</b><br/> centos7-matrix</td>
- <td><b>Vagrant Definition</b><br/> releng/builder/vagrant/basic-java-node</td>
- <td><b>Spinup Script</b><br/> releng/builder/jenkins-scripts/matrix.sh</td>
- </tr>
- <tr>
- <td colspan="4">
- This is a very minimal system that is designed to spin up with 2 build
- instances on it. The purpose is to have a location that is not the
- Jenkins master itself for jobs that are executing matrix operations
- since they need a director location. This image should not be used for
- anything but tying matrix jobs before the matrx defined label ties.
- </td>
- </tr>
-
- <tr class="warning">
- <td><b>Jenkins Label</b><br/> dynamic_robot</td>
- <td><b>Minion Template name</b><br/> centos7-robot</td>
- <td><b>Vagrant Definition</b><br/> releng/builder/vagrant/integration-robotframework</td>
+ <td><b>Jenkins Labels</b><br/> centos7-robot-2c-2g</td>
+ <td><b>Minion Template names</b><br/> centos7-robot-2c-2g</td>
+ <td><b>Packer Template</b><br/>
+ releng/builder/packer/templates/robot.json</td>