manageiq/manageiq-cross_repo-tests

ManageIQ cross-repository testing framework tests

ManageIQ cross-repository testing framework tests

This repo is used to execute cross-repository tests for the ManageIQ project.

Usage

In order to use this repo, create a pull request modifying the .travis.yml file and setting the TEST_REPO and REPOS environment variables as needed.

For more information about the variables or more examples, refer to the manageiq-cross_repo gem.

Examples

Testing a single repo in the context of ManageIQ PR 12345

@@ -14,6 +14,6 @@ matrix:
   fast_finish: true
 env:
   global:
-  - REPOS=
+  - REPOS=manageiq#12345
   matrix:
-  - TEST_REPO=
+  - TEST_REPO=manageiq-ui-classic

Testing multiple repos in the context of ManageIQ PR 12345

@@ -14,6 +14,7 @@ matrix:
   fast_finish: true
 env:
   global:
-  - REPOS=
+  - REPOS=manageiq#12345
   matrix:
-  - TEST_REPO=
+  - TEST_REPO=manageiq-ui-classic
+  - TEST_REPO=manageiq-api

Testing multiple repos in the context of ManageIQ branch "gaprindashvili"

@@ -14,6 +14,7 @@ matrix:
   fast_finish: true
 env:
   global:
-  - REPOS=
+  - REPOS=manageiq@gaprindashvili
   matrix:
-  - TEST_REPO=
+  - TEST_REPO=manageiq-ui-classic
+  - TEST_REPO=manageiq-api

Same syntax is used for tags

License

Open source under the terms of the MIT License.

manageiq-cross_repo-tests's Issues

Use the hidden merge commit when testing PRs

Sometimes a PR branch could be out of date yet still mergeable since there are no conflicting changes in the PR. However when the cross-repo tests run, they aren't necessarily testing the result of merging the PR because dependencies or other code on the merge target may have changed since the PR branch was last rebased. Sometimes the tests fail because bundler can't resolve dependencies because they are stale in the PR, but updated in master.

For better results we could checkout the PR merge ref rather than the PR head and run tests against that.

Based on discussion in manageiq/core March 3, 2020 10:03 AM