tree d073b05e6144b407f91e3b1346c800f6687fcbda
parent 4569bf49daaebff06be0482426908bb5497fad08
author Ed Tanous <edtanous@google.com> 1629398349 -0700
committer Andrew Geissler <geissonator@yahoo.com> 1632257001 +0000

Add the concept of a "repo test"

This commit adds a custom target called "repotest" to the build scripts,
which triggers tests to be run on the openbmc/openbmc repository.   It
attempts to call the script in meta-phosphor, being added in this
commit.   https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/46743
Adding the custom target isn't the obvious approach, but considering
that the jenkins job is currently a multi-axis build, and we only want
to run this test once, it seemed like the best option, although I'm open
to alternatives.

This will need an update to add repotest to the jenkins axis before
these builds will start enforcing.

Tested:
Ran target=repotest ./build-setup.sh
and saw "Repo test passed" in the output.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I6caef6c28ee70f3c6194b9ea96cda8cfb58eb443