...
Here is a table summarizing the most common variables in use , details below in the relevant SCM section
...
Note |
---|
For latestCommit parameter, we’re highlighting the short version in the screenshots below but the long/entire SHA identifier needs to be used. |
GitHub
...
If you’re using the GitHub Actions or the GitHub Pull Request Builder plugin for Jenkins, you can use the following mapping to environment variables provided by the pluginvariables suggested below
Sealights PR Parameter | GitHub | Pull Request Actions variables | GitHub PR Builder variables (Jenkins plugin) | Comment |
---|---|---|---|---|
pullRequestNumber |
|
| ||
latestCommit |
|
| ||
repoUrl |
|
| Something similar to: https://github.mycompany.com/myappjava/ if the pull request URL is | |
targetBranch |
|
| This is the branch name itself and might need to have a prefix added (Like: "origin/") to match the branch that was provided to SeaLights when scanning the merged branch |
...
Sealights PR Parameter | Bamboo Build env. variables | Comment |
pullRequestNumber | Please refer to the workaround(s) shared in the comments of this Bamboo support page: https://jira.atlassian.com/browse/BAM-18350 | |
latestCommit |
| |
repoUrl |
| |
targetBranch |
| The base reference name of the webhook event that triggered the build. It is the branch reference for pull requests (i.e. target branch). |
...
Sealights PR Parameter | env. variables | Comment |
pullRequestNumber |
| |
latestCommit | The default environment ADO variable | |
repoUrl |
| |
targetBranch |
| This is the branch name itself and might need some string manipulation to remove a prefix added (Like: "refs/heads/") to match the branch that was provided to SeaLights when scanning the merged branch. |
Info |
---|
More details for ADO/TFS variables may be found in the official documentation: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables |
...