frogbot scan-pull-request gradle error when artifactory plugin used
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Describe the bug
Running frogbot scan-pull-request in GitLab ci job ends with an error.
The issue is related to using the Gradle Artifactory plugin.
The same issue happens with jfrog-cli command jf audit.
But with setting the config option jf gradle-config --uses-plugin it works. As described in https://github.com/jfrog/jfrog-cli/issues/1404
Current behavior
Error:
An exception occurred applying plugin request [id: 'com.jfrog.artifactory', version: '4.29.4']
> Failed to apply plugin 'com.jfrog.artifactory'.
> Cannot cast object 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention@da6fc6c' with class 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention' to class 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'
Reproduction steps
Use Gradle Artifactory plugin in the project
Set jf gradle-config --uses-plugin
Run frogbot scan-pull-request
Expected behavior
The option --uses-plugin is applied to frogbot the same as for jfrog-cli
JFrog Frogbot version
2.4.1
Package manager info
Gradle 7.6
Git provider
GitLab
JFrog Frogbot configuration yaml file
No response
Operating system type and version
Alpine Linux 3.17
JFrog Xray version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce frogbot scan-pull-request in a GitLab CI job using Gradle 7.6, the Artifactory plugin version 4.29.4, Frogbot 2.4.1, and Alpine Linux 3.17; compare it with jf gradle-config --uses-plugin. Trace the scan-pull-request configuration path and make the --uses-plugin setting apply to Frogbot without the plugin cast error, then verify the reproduction succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100