We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
env.BRANCH_NAME is only present in multi-branch pipeline builds, regular pipelines don't have information about branches.
env.BRANCH_NAME
Affected methods:
Git.getBranchName()
SonarQube.initMavenForRegularAnalysis()
We could use git rev-parse --abbrev-ref HEAD in Git class, instead. SonarQube could use Git class. Keeps everything DRY.
git rev-parse --abbrev-ref HEAD
Git
When fixed, update README.
The text was updated successfully, but these errors were encountered:
#16 Fixes BRANCH_NAME=null for SQ analyses in non-multi-branch pipelines
68e7f52
No branches or pull requests
env.BRANCH_NAME
is only present in multi-branch pipeline builds, regular pipelines don't have information about branches.Affected methods:
Git.getBranchName()
SonarQube.initMavenForRegularAnalysis()
We could use
git rev-parse --abbrev-ref HEAD
inGit
class, instead. SonarQube could use Git class. Keeps everything DRY.When fixed, update README.
The text was updated successfully, but these errors were encountered: