-
-
Notifications
You must be signed in to change notification settings - Fork 534
New issue
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
Could not decorate Pull Request on Github #90
Labels
bug
Something isn't working
Comments
I think this may be an error in the code: Line 92 in fdb382a
Line 67 in fdb382a
I think that that first block should be String projectPath = projectAlmSettings.getAlmRepo() , although I can't remember if that path is project/repo or just repo .
|
@mc1arke I made the change you said and it's working. Should I open a PR? |
Yes please. |
mc1arke
pushed a commit
that referenced
this issue
Feb 20, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
Fixed in #92 |
mc1arke
pushed a commit
that referenced
this issue
Apr 19, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
mc1arke
pushed a commit
that referenced
this issue
Apr 20, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
mc1arke
pushed a commit
that referenced
this issue
May 17, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
mc1arke
pushed a commit
that referenced
this issue
May 17, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
mc1arke
pushed a commit
that referenced
this issue
Jun 7, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
mc1arke
pushed a commit
that referenced
this issue
Jun 7, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
mc1arke
pushed a commit
that referenced
this issue
Jun 7, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
mc1arke
pushed a commit
that referenced
this issue
Jun 7, 2020
The Github ALM Binding Web Service uses the `AlmRepo` field to store the repository name, but the Github decorator was using `AlmSlug` to try and retrieve the repository name, so was getting a `null` value back and failing to find a matching repository. Switching to using `AlmRepo` in the decorator overcomes this issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Github decorator not working
To Reproduce
Steps to reproduce the behavior:
ce.log
file:Expected behavior
Pull request decorator on github pull request.
Software Versions
Additional context
sonarqube-community-branch-plugin/src/main/java/com/github/mc1arke/sonarqube/plugin/ce/pullrequest/github/v3/RestApplicationAuthenticationProvider.java
Line 114 in fdb382a
projectPath
is null, I tried to debug why with no success.I guess there is some configuration missing, but I don't know which one.
The text was updated successfully, but these errors were encountered: