[
https://issues.jenkins-ci.org/browse/JENKINS-13926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Linus Tolke updated JENKINS-13926:
----------------------------------
Description:
According to a comment in issue JENKINS-5786 the options specified in the
per-job MAVEN_OPTS field overrides the options specified in the Global
MAVEN_OPTS field. The strange thing is that the per-job MAVEN_OPTS field seems
to be used for two different purposes, both to control the per-job MAVEN_OPTS
and to show the Global MAVEN_OPTS. There is also a risk that a user will
inadvertently create a per-job MAVEN_OPTS setting when he did not mean to.
When the per-job MAVEN_OPTS is specified everything is working as expected. The
entered value is used in the jobs.
If the per-job MAVEN_OPTS is erased in the per-job configuration, and the
configuration is saved, the Global MAVEN_OPTS is used in the per-job
configuration. This is as expected. When opening the configuration page for the
job again the per-job MAVEN_OPTS field shows the Global MAVEN_OPTS value. If
that configuration is saved, the copy of the Global MAVEN_OPTS value becomes
the per-job MAVEN_OPTS. To avoid setting a per-job MAVEN_OPTS the user would
have to empty this field every time it is watched.
Suggested solutions:
I would like to remove the feature of showing the Global MAVEN_OPTS in the
per-job MAVEN_OPTS field and instead add a text below the field stating:
"If left empty, the Global MAVEN_OPTS will be used and they are currently set
to <BLABLA>"
This would give the user better control on when a job is configured with a
per-job MAVEN_OPTS and when it is using the Global MAVEN_OPTS.
The problem described in JENKINS-12264 might be the same one in that there is
no distinction between the "use Global MAVEN_OPTS" and "use previously saved
copy of Global MAVEN_OPTS".
was:
According to a comment in issue JENKINS-5786 the options specified in the
per-job MAVEN_OPTS field overrides the options specified in the Global
MAVEN_OPTS field. The strange thing is that the per-job MAVEN_OPTS field seems
to be used for two different purposes, both to control the per-job MAVEN_OPTS
and to show the Global MAVEN_OPTS. There is also a risk that a user will
inadvertently create a per-job MAVEN_OPTS setting when he did not mean to.
When the per-job MAVEN_OPTS is specified everything is working as expected. The
entered value is used in the jobs.
If the per-job MAVEN_OPTS is erased in the per-job configuration, and the
configuration is saved, the Global MAVEN_OPTS is used in the per-job
configuration. This is as expected. When opening the configuration page for the
job again the per-job MAVEN_OPTS field shows the Global MAVEN_OPTS value. If
that configuration is saved, the copy of the Global MAVEN_OPTS value becomes
the per-job MAVEN_OPTS. To avoid setting a per-job MAVEN_OPTS the user would
have to empty this field every time it is watched.
Suggested solutions:
I would like to remove the feature of showing the Global MAVEN_OPTS in the
per-job MAVEN_OPTS field and instead add a text below the field stating:
"If left empty, the Global MAVEN_OPTS will be used and they are currently set
to <BLABLA>"
This would give the user better control on when a job is configured with a
per-job MAVEN_OPTS and when it is using the Global MAVEN_OPTS.
> The relation between the Global MAVEN_OPTS and the job-specific MAVEN_OPTS
> --------------------------------------------------------------------------
>
> Key: JENKINS-13926
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13926
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Environment: Linux (Ubuntu)
> Reporter: Linus Tolke
> Priority: Minor
> Labels: configuration, maven2,, options
>
> According to a comment in issue JENKINS-5786 the options specified in the
> per-job MAVEN_OPTS field overrides the options specified in the Global
> MAVEN_OPTS field. The strange thing is that the per-job MAVEN_OPTS field
> seems to be used for two different purposes, both to control the per-job
> MAVEN_OPTS and to show the Global MAVEN_OPTS. There is also a risk that a
> user will inadvertently create a per-job MAVEN_OPTS setting when he did not
> mean to.
> When the per-job MAVEN_OPTS is specified everything is working as expected.
> The entered value is used in the jobs.
> If the per-job MAVEN_OPTS is erased in the per-job configuration, and the
> configuration is saved, the Global MAVEN_OPTS is used in the per-job
> configuration. This is as expected. When opening the configuration page for
> the job again the per-job MAVEN_OPTS field shows the Global MAVEN_OPTS value.
> If that configuration is saved, the copy of the Global MAVEN_OPTS value
> becomes the per-job MAVEN_OPTS. To avoid setting a per-job MAVEN_OPTS the
> user would have to empty this field every time it is watched.
> Suggested solutions:
> I would like to remove the feature of showing the Global MAVEN_OPTS in the
> per-job MAVEN_OPTS field and instead add a text below the field stating:
> "If left empty, the Global MAVEN_OPTS will be used and they are currently set
> to <BLABLA>"
> This would give the user better control on when a job is configured with a
> per-job MAVEN_OPTS and when it is using the Global MAVEN_OPTS.
> The problem described in JENKINS-12264 might be the same one in that there is
> no distinction between the "use Global MAVEN_OPTS" and "use previously saved
> copy of Global MAVEN_OPTS".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
