| commit | 55448adb2d4a975e39a3ff991493b686f92ed6a5 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Dec 14 14:28:28 2020 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 17 11:54:48 2020 -0600 |
| tree | dd86ce74d70dbbd6d0cbb2e7a09637772b736bfd | |
| parent | 298d56b3b798abc340eb34a4f300604dacbca5bb [diff] |
unit-test: allow non-shell scripts for extensions
The unit-test script currently allows extension scripts of the
name 'run-ci.sh', but there are examples within openbmc where
the extensions are not actually shell (at least one is Python).
Remove the extension requirement on the script by looking both
for 'run-ci.sh' and 'run-ci'.
Tested the 'find_file' script with:
> find_file('run-ci', '.../openbmc-sources')
['.../openbmc-sources/phosphor-dbus-interfaces/run-ci']
> find_file('run-ci.sh', '.../openbmc-sources')
['.../openbmc-sources/phosphor-logging/extensions/openpower-pels/registry/run-ci.sh',
'.../openbmc-sources/phosphor-power/phosphor-regulators/test/run-ci.sh',
'.../openbmc-sources/entity-manager/scripts/run-ci.sh' ]
> find_file(['run-ci', 'run-ci.sh'], '.../openbmc-sources')
['.../openbmc-sources/phosphor-dbus-interfaces/run-ci',
'.../openbmc-sources/phosphor-logging/extensions/openpower-pels/registry/run-ci.sh',
'.../openbmc-sources/phosphor-power/phosphor-regulators/test/run-ci.sh',
'.../openbmc-sources/entity-manager/scripts/run-ci.sh']
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib420c69e88e88ca0a50863c83ad43fac750d3e7a
Build script for CI jobs in Jenkins.