[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title
Victor Ott edited a comment on JENKINS-39268
Re: Properties are not passed to maven command by maven integration plugin
The problem lies within class {{hudson.tasks.Maven}}, which afaik is part of "core" Jenkins, and was introduced with following commit:[https://github.com/jenkinsci/jenkins/commit/e66e719f1e6caa54b546a5bdee5ab062089d21c2]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott commented on JENKINS-39268 Re: Properties are not passed to maven command by maven integration plugin The problem lies within class hudson.tasks.Maven, and was introduced with following commit: https://github.com/jenkinsci/jenkins/commit/e66e719f1e6caa54b546a5bdee5ab062089d21c2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-39268 Properties are not passed to maven command by maven integration plugin Change By: Victor Ott Component/s: core Component/s: maven-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott edited a comment on JENKINS-39268 Re: Properties are not passed to maven command by maven integration plugin I can confirm this issue with following versions:* Jenkins ver. 2.19.2 (LTS)* Maven Integration plugin 2.14* SUSE Linux Enterprise Server 11 (x86_64) Patch 4 * Java build 1.8.0_92-b14, 64-Bit Server VM (build 25.92-b14, mixed mode) Note: if you set the checkbox "Inject build variables", then not only all job parameters are injected into the Maven command line, as expected, BUT also the definitions from "Properties" sections. This is not the expected behaviour.In my opinion this isn't a minor issue, because it affects LOTS of jobs, without error messages, and it causes therefore inconsistent builds without anyone noticing that! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott edited a comment on JENKINS-39268 Re: Properties are not passed to maven command by maven integration plugin I can confirm this issue with following versions:* Jenkins ver. 2.19.2 (LTS)* Maven Integration plugin 2.14* SUSE Linux Enterprise Server 11 (x86_64) Patch 4Note: if you set the checkbox "Inject build variables", then not only all job parameters are injected into the Maven command line, as expected, BUT also the definitions from "Properties" sections. This is not the expected behaviour.In my opinion this isn't a minor issue, because it affects LOTS of jobs, without error messages, and it causes therefore inconsistent builds without anyone noticing that! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott edited a comment on JENKINS-39268 Re: Properties are not passed to maven command by maven integration plugin I can confirm this issue with following versions:* Jenkins ver. 2.19.2 (LTS)* Maven Integration plugin 2.14* SUSE Linux Enterprise Server 11 (x86_64) Patch 4Note: if you set the checkbox "Inject build variables", then the definitions from "Properties" sections not only all job parameters are injected into the Maven command line, as expected, BUT together with ALL job parameters also the definitions from "Properties" sections . This is in not the expected behaviour.In my opinion not this isn't a minor issue, because it affects LOTS of jobs, without error messages, and therefore inconsistent builds without noticing that! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott edited a comment on JENKINS-39268 Re: Properties are not passed to maven command by maven integration plugin I can confirm this issue with following versions:* Jenkins ver. 2.19.2 (LTS)* Maven Integration plugin 2.14* SUSE Linux Enterprise Server 11 (x86_64) Patch 4Note: if you set the checkbox "Inject build variables", then the definitions from "Properties" sections are injected into the Maven command line, BUT together with ALL job parameters.This is in my opinion not a minor issue, because it affects LOTS of jobs, without error messages . , and therefore inconsistent builds without noticing that! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-39268 Properties are not passed to maven command by maven integration plugin Change By: Victor Ott Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott edited a comment on JENKINS-39268 Re: Properties are not passed to maven command by maven integration plugin I can confirm this issue with following versions:* Jenkins ver. 2.19.2 (LTS)* Maven Integration plugin 2.14* SUSE Linux Enterprise Server 11 (x86_64) Patch 4Note: if you set the checkbox "Inject build variables", then the definitions from "Properties" sections are injected into the Maven command line, BUT together with ALL job parameters. This is in my opinion not a minor issue, because it affects LOTS of jobs, without error messages. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Victor Ott commented on JENKINS-39268 Re: Properties are not passed to maven command by maven integration plugin I can confirm this issue with following versions: Jenkins ver. 2.19.2 (LTS) Maven Integration plugin 2.14 SUSE Linux Enterprise Server 11 (x86_64) Patch 4 Note: if you set the checkbox "Inject build variables", then the definitions from "Properties" sections are injected into the Maven command line, BUT together with ALL job parameters. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-39268 Properties are not passed to maven command by maven integration plugin Change By: Oleg Nenashev Component/s: maven-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39268) Properties are not passed to maven command by maven integration plugin
Title: Message Title Michael Nachtigal created an issue Jenkins / JENKINS-39268 Properties are not passed to maven command by maven integration plugin Issue Type: Bug Assignee: Unassigned Attachments: fails.png, succeeds.png Components: core Created: 2016/Oct/26 2:40 PM Environment: ubuntu linux 15.10 64bit jenkins v2.27 maven integration plugin v2.14 Priority: Minor Reporter: Michael Nachtigal The command I'm trying to get jenkins to execute is like this: mvn -Dparam1=val1 -Dparam2=val2 -f bdd/pom.xml test My pom.xml has param1 and param2 properties whose values need to be passed in to work, and the above command, when run manually, works. When I try to set that command up as shown in the fails.png screenshot I attached (putting param1 and param2 in the Properties field, as the help/hint states I should), they are not provided in the maven command (confirmed with jenkins console output and observation that the build fails because of those missing values). As a workaround, I can provide them explicitly in the Goals section (as shown by succeeds.png), but that strikes me as a hack, given the way the maven integration plugin separates goals and properties into separate input fields.
