7b1c47711d
The plugin uses a different matrix execution strategy. I have refactored the part of code assuming there is only one strategy. The previous one is known as 'default' and this change is back compatible. Drop an error whenever more than one strategy is used. Support exclude rules from either a file or inlined YAML (note in the later case the YAML will need to be a literal string). Tweak axis type documentation to reference both built-in axes and ones provided by additional plugins. Include three different examples for Yaml Axis which would help end users understand how to add support for exclusion and or specificy the exclusion as inlined Yaml. Change-Id: I18e0fc7cb525fba3b772bae10e81d8dfce7298cb
30 lines
979 B
XML
30 lines
979 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<matrix-project>
|
|
<executionStrategy class="org.jenkinsci.plugins.yamlaxis.YamlMatrixExecutionStrategy">
|
|
<yamlType>file</yamlType>
|
|
<yamlFile>exclude.yaml</yamlFile>
|
|
<yamlText/>
|
|
<excludeKey>exclude</excludeKey>
|
|
</executionStrategy>
|
|
<axes>
|
|
<org.jenkinsci.plugins.yamlaxis.YamlAxis>
|
|
<name>python</name>
|
|
<values>
|
|
<string>config.yaml</string>
|
|
</values>
|
|
</org.jenkinsci.plugins.yamlaxis.YamlAxis>
|
|
<org.jenkinsci.plugins.yamlaxis.YamlAxis>
|
|
<name>database</name>
|
|
<values>
|
|
<string>config.yaml</string>
|
|
</values>
|
|
</org.jenkinsci.plugins.yamlaxis.YamlAxis>
|
|
</axes>
|
|
<actions/>
|
|
<keepDependencies>false</keepDependencies>
|
|
<blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
|
|
<blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
|
|
<concurrentBuild>false</concurrentBuild>
|
|
<canRoam>true</canRoam>
|
|
</matrix-project>
|