Loading
Use relative path instead of absolute path for gradle command
- Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.
What does this MR do?
Use "gradle" default gradle command
No other builder specifies an absolute path to its command.
For example, the maven builder uses "mvn" https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium/-/blob/f4f663bbbf9119ab377ab876f9a268e99a50b939/builder/maven/maven.go#L66 and the pip builder uses "pip3" https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium/-/blob/f4f663bbbf9119ab377ab876f9a268e99a50b939/builder/pip/pip.go#L23
Gradle should be consistent with the other builders.
This minor change allows using the builder when "gradle" is not at /opt/asdf/shims/gradle or if a different gradle is desired.
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
- Changelog entry added
- Documentation created/updated for GitLab EE, if necessary
- Documentation created/updated for this project, if necessary
- Documentation reviewed by technical writer or follow-up review issue created
- Tests added for this feature/bug
- Job definition updated, if necessary
- Conforms to the code review guidelines
- Conforms to the Go guidelines
- Security reports checked/validated by reviewer
Edited by Oscar Tovar