-
Notifications
You must be signed in to change notification settings - Fork 75
Integration tests
After you opened a PR the 'health-ok' suite will be triggered.
If you want to run more tests against your PR you can simply trigger these by leaving comments. Depending on your needs, we currently have implemented tests for:
please run basic suite
please run dmcrypt suite
please run ganesha suite
please run igw suite
please run mds suite
please run openattic suite
please run rgw suite
To inspect the logs you can click on the 'Deepsea's health-ok check detail button' which will appear on Github's Status Check bar on the very bottom of your PR. This will redirect you to a Jenkins instance and present you with the page of the job you just triggered. By clicking on 'default' you reach the 'Build artifacts' page where you can inspect a log file called: teuth-deepsea-b[id].log.
Inside this log you have to look for a URL that looks similar to this.
Depending on which suite you ran, you will see the output of all stages in 'debug' verbosity.
You can rerun a test by simply deleting the comment and re-posting the trigger phrase again. (Jenkins' 're-run' feature is not enabled currently.)
- Prerequisites
- Manual Installation
- Custom Profiles
- Alternate Installations
- Automated Installation
- Purging
- Reinstallation
- Replacing an OSD
- Inspecting the Configuration
- Understanding Pathnames and Arguments
- Overriding Default Settings
- Overriding Default Steps
- Man Pages
- deepsea.1
- deepsea.7
- deepsea-commands.7
- deepsea-minions.7
- deepsea-monitor.1
- deepsea-policy.cfg.5
- deepsea-stage.1
- deepsea-stage-dry-run.1
- deepsea-stage-run.1
- deepsea-stages.7
- Backporting
- Testing
- Branches & Releases