...
Configure the pull request flow to merge from the target branch (even if done locally) prior to running the build scanner
| Code Block | ||
|---|---|---|
| ||
//retrieve the PR source code from the Git based SCM git clone git@github.repo/repo.git //create a local integration branch starting from the target branch - do not push it to the remote git checkout branch_name -b <local-integration-branch-name> <target-branch> //Merge pull request into local integration branch git pull --ff git@github.repo/repo.git <pull-request-branch> ... //run sealights build |
Cause #2
The target branch contains commits that were not reported to sealights SeaLights and the user merged from the target branch to the pull request branch.
| Note |
|---|
A common reason is with target branch that have builds reported based on predefined frequency (hourly, daily) rather than after every single merge (commit) to that branch. |
...
Solution #2
Validate in the CI server (Jenkins, Bamboo…) that the last every commit from the SCM (target branch) was is reported to Sealights via a an automated build.
If not, initiate a build from both the target branch and then the PR branch.
...