| Table of Contents |
|---|
Benefits
...
...
SeaLights Pull Request Integration expose Quality Risks to the developer, as part of the Pull Request process to be handled early enough in the development process.
This capability helps your organization to mitigate risk by identifying Quality Risks for the developer before the Merge is done
- Works on any Merge/Branch level
- Ability to define if Quality Risks block the Merge
Below, a simple 3 steps plan for deployment of this functionality for your benefit.
Step 1 - Install GitHub App for Pull Request Analysis by Sealights
...
According to the Travis Official documentation, the TRAVIS CI Integration should use the following environment variables based on the mapping below:
Sealights' Parameter | Travis CI Env. Variable | Comment |
|---|---|---|
| latestCommit | TRAVIS_PULL_REQUEST_SHA, | |
| pullRequestNumber | TRAVIS_PULL_REQUEST | |
| repoUrl | TRAVIS_REPO_SLUG | You may need to prepend the base URL of your Github repository, like "https://github.com/$TRAVIS_REPO_SLUG" |
| targetBranch | TRAVIS_BRANCH | You may need to prepend "origin/" to the branch exact matching. |
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
language: java install: - wget https://agents.sealights.co/sealights-java/sealights-java-latest.zip - unzip sealights-java-latest.zip before_script: - export SL_PR_REPO="https://www.github.com/$TRAVIS_REPO_SLUG" - java -jar sl-build-scanner.jar -prConfig -appname "MyApp-Master" -latestCommit $TRAVIS_PULL_REQUEST_SHA -pullRequestNumber $TRAVIS_PULL_REQUEST -repoUrl $SL_PR_REPO -targetBranch origin/$TRAVIS_BRANCH -tokenfile sl_acc_token.txt -pi "*co.sealights.sample.*" -enableNoneZeroErrorCode script: # Sealights is predefined in the POM Profile - mvn clean test |
...