jfrog / jfrog/frogbot

support passing options to maven on-the-fly

Open
#181 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Go
Stars
372
Forks
107
Avg merge
2d 20h
Merged PRs (30d)
5

Description

Is your feature request related to a problem? Please describe.
I would like to be able to pass a maven option on-the-fly e.g. -DdisableX=true

(currently our builds try and extract a git branch from the working directory, and it seems that the base branch audit is downloaded as an archive and untarred and results in bare code- we can disable this on the fly e.g. -DdisableX=true, but can't find a way to pass this into frogbot job)

Describe the solution you'd like to see

A JF_MAVEN_ARGS env var to pass options specific to the frogbot run

Describe alternatives you've considered

  • MAVEN_ARGS is not supported until maven version 4.x.x - https://maven.apache.org/configure.html
  • Options can be set in .mvn/maven.config but I don't want to generally apply those options to all builds.
  • copying in maven.config with an earlier workflow step doesn't get used when auditing the base branch

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the frogbot job invokes Maven and how the base-branch audit is run. Review the requested JF_MAVEN_ARGS environment variable alongside .mvn/maven.config and the workflow step that copies it. Done means Maven options supplied through JF_MAVEN_ARGS are applied to the frogbot run without changing the repository's general build configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.