[WIP] initiall version of PR test jobs #11
Conversation
|
The Jobs are visible on tendrl-PR CentOS CI Jenkins page and are named |
dahorak
force-pushed
the
pr-test-jobs
branch
from
be1d3cc to
0de0a22
Compare
|
@TimothyAsir Please review this |
| - github-pull-request: | ||
| admin-list: | ||
| - dahorak | ||
| white-list: |
There was a problem hiding this comment.
Is there a way to input this rather than hardcoding
There was a problem hiding this comment.
It's the same as for the build jobs. Itshould be possible, to automatically fetch the list of people from the organization specified below in the org-list section, but there seems to be some problem with this and I'm not sure why it doesn't work and where might be the problem with that.
I'll try to check that once more and find some more information about that - that will be definitely the best solution.
| property-file: env.sh | ||
| block: true | ||
|
|
||
| publishers: |
There was a problem hiding this comment.
Where the test results will be posted?
There was a problem hiding this comment.
The overall status of the installation and tests is reported back to the PR where it was triggered (as a CentOS CI - tests line in the checks section) and Details link points to the particular job.
More granular results are available in the subsequent jobs (see Subproject Builds section of the Jenkins job).
Additionally when it fails, it will notify me over email, so I can check if it is real installation or test failure, or if it is problem with the tests itself.
* use tendrl/tendrl copr repo, instead of tendrl/release repo
- limit the job execution only for PR updates
dahorak
force-pushed
the
pr-test-jobs
branch
from
f962f82 to
be4dd70
Compare
- changes related to usage of tendrl-ansible changes
- it is not possible to send emails to this list outside of RH (from ci@centos.org)
3 participants
Fixes #10
Jobs for launching test suite for every PR.
It will create one job for each repository.
The job might be triggered by
run testsphrase in the respective PR.It is possible to specify dependencies on PRs from other repos this way:
Depends on: tendrl-ui/pr809 tendrl-notifier/pr153either in the PR description or in the comment triggering the test execution (or on both places).
It has to be on one line without any additional formatting and has to follow quite precisely this format, to be able to correctly (and easily) parse it.
Basically the line has to start with
depends on:string (case insensitive) followed by space separated list of dependencies in the form of:<reponame>/pr<id>, where<reponame>is the name of the repository (includingtendrl-prefix) and<id>is the PR number.