[JIRA] (JENKINS-48912) Regression: empty "host: " header causes "400 Bad Request"
Title: Message Title Victor Ott commented on JENKINS-48912 Re: Regression: empty "host: " header causes "400 Bad Request" Can't wait to see the fix released... This is such a blocker issue for us! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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 build step
Title: Message Title Victor Ott closed an issue as Fixed First LTS version containing fix is 2.32.2 Jenkins / JENKINS-39268 Properties are not passed to Maven command by Maven build step Change By: Victor Ott Status: Resolved Closed Assignee: Victor Ott Michael Nachtigal 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
[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Victor Ott commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" Is it ok for everybody if we close this ticket as duplicate of JENKINS-32167 ? 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-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Victor Ott edited a comment on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" @[~jglick] Thanks for the pointer to JENKINS-32167. I've added + [more details there in a comment|https://issues.jenkins-ci.org/browse/JENKINS-32167?focusedCommentId=286800=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-286800] + . 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-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Victor Ott commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" @Jesse Glick Thanks for the pointer to JENKINS-32167. I've added more details there in a comment. 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-32167 ISVNAuthentication provider did not provide credentials Change By: Victor Ott Attachment: screenshot01.png 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-32167 ISVNAuthentication provider did not provide credentials Change By: Victor Ott Attachment: screenshot01.png 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Victor Ott commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials We experience this same issue, pure Linux environment: Linux x86_64, Kernel 3.0.101-65-default JDK8 64bit Jenkins ver. 2.19.4 Subversion Plugin 2.7.1 All affected jobs have SVN checkouts with externals (externals pointing to relative locations, on same server). All SVN configured projects/jobs are matching the SVN realm. Adding a second credential to the checkout configurations, with exactly the same parameters as the first credential, can only be a test workaround, and I'll apply that to only two jobs. Here two examples of affected jobs: 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-32167 ISVNAuthentication provider did not provide credentials Change By: Victor Ott Attachment: screenshot02.png 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-32167 ISVNAuthentication provider did not provide credentials Change By: Victor Ott Attachment: screenshot01.png 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-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott commented on JENKINS-38850 Re: Multijob runs one parameterized child job instead of running multiple child jobs with different parameters I've created a pull request, containing a test reproducing the issue: https://github.com/jenkinsci/tikal-multijob-plugin/pull/106 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-32167 ISVNAuthentication provider did not provide credentials Change By: Victor Ott Environment: Windows 7; Jenkins 1.617 with Subversion Plug-in 2.5.5Windows Server 2012 R2; Jenkins 2.19.3 with Subversion plugin 2.7.1 Linux x86_64, Jenkins 2.19.4 with Subversion Plugin 2.7.1 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-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-31455 Build instability with "ISVNAuthentication provider did not provide credentials" Change By: Victor Ott Environment: Windows Server 2012 R2; Jenkins 2.19.3 with Subversion plugin 2.7.1 Linux x86_64, 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-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-31455 Build instability with "ISVNAuthentication provider did not provide credentials" Change By: Victor Ott Environment: Windows Server 2012 R2; Jenkins 2.19.3 with Subversion plugin 2.7.1Linux x86_64,Linux x86_64 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-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-31455 Build instability with "ISVNAuthentication provider did not provide credentials" Change By: Victor Ott Environment: Windows Server 2012 R2; Jenkins 2.19.3 with Subversion plugin 2.7.1Linux x86_64, Linux x86_64 Jenkins ver. 2.19.4 with Subversion Plugin 2.7.1 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-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Victor Ott commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" We experience this same issue, but under Linux : Linux x86_64, Kernel 3.0.101-65-default JDK8 64bit Jenkins ver. 2.19.4 Subversion Plugin 2.7.1 No build pipelines, but multijobs, maybe also some freestyle jobs. 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 build step
Title: Message Title Victor Ott edited a comment on JENKINS-39268 Re: Properties are not passed to Maven command by Maven build step Fix should be available starting with Jenkins 2. 38 39 . 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 build step
Title: Message Title Victor Ott edited a comment on JENKINS-39268 Re: Properties are not passed to Maven command by Maven build step Fix should be available starting with Jenkins 2.38. 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 build step
Title: Message Title Victor Ott updated JENKINS-39268 Fix should be available with Jenkins 2.38. Jenkins / JENKINS-39268 Properties are not passed to Maven command by Maven build step Change By: Victor Ott Status: In Review Resolved Resolution: Fixed 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
[JIRA] (JENKINS-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott commented on JENKINS-38850 Re: Multijob runs one parameterized child job instead of running multiple child jobs with different parameters Changed priority to blocker, because builds are skipped when this bug triggers, without any notice. 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-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-38850 Multijob runs one parameterized child job instead of running multiple child jobs with different parameters Change By: Victor Ott Priority: Major Blocker 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-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title
Victor Ott edited a comment on JENKINS-38850
Re: Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
I'm "glad" someone else experienced this too...Configuration:* Jenkins 2.19.4* Multijob Plugin 1.21* EnvInject Plugin 1.93.1* Token Macro Plugin 2.0* Parameterized Trigger Plugin 2.32Six weeks ago we updated some plugins, including Multijob Plugin 1.21 => 1.23. Since then we started missing job builds.Today I rolled back only the Multijob Plugin 1.23 => 1.21, and the issue dissapeared.I've assembled some test jobs and have let them run extensively, with following structure!multijob-structure.png!where the {{~worker}} job can run in parallel.The {{~X1}} .. {{~X5}} jobs invoke the {{~worker}} job with different parameters, that's 100% sure (see attached XML job configuration files).With Multijob Plugin 1.23 some (up to all) {{~worker}} invocations are merged, and the resulting build receives the parameters of one of the merged invocations, here an example:!job-builds-merged.png!As [~joanroch] already noted, the problem occurs only if the build number (ID) of the upstream jobs {{~X1}} .. {{~X5}} is the same. If you start one of the upstream jobs few times separately, thus increasing its "next build number" to a number != to the other build numbers, that upstream job will reliably invoke the downstream job.
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
[JIRA] (JENKINS-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title
Victor Ott edited a comment on JENKINS-38850
Re: Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
I'm "glad" someone else experienced this too...Configuration:* Jenkins 2.19.4* Multijob Plugin 1.21* EnvInject Plugin 1.93.1* Token Macro Plugin 2.0* Parameterized Trigger Plugin 2.32Six weeks ago we updated some plugins, including Multijob Plugin 1.21 => 1.23. Since then we started missing job builds.Today I rolled back only the Multijob Plugin 1.23 => 1.21, and the issue dissapeared.I've assembled some test jobs and have let them run extensively , with following structure!multijob-structure.png!where the {{~worker}} job can run in parallel.The {{~X1}} .. {{~X5}} jobs invoke the {{~worker}} job with different parameters, that's 100% sure (see attached XML job configuration files).With Multijob Plugin 1.23 some (up to all) {{~worker}} invocations are merged, and the resulting build receives the parameters of one of the merged invocations, here an example:!job-builds-merged.png!As [~joanroch] already noted, the problem occurs only if the build number (ID) of the upstream jobs {{~X1}} .. {{~X5}} is the same. If you start one of the upstream jobs few times separately, thus increasing its "next build number" to a number != to the other build numbers, that upstream job will reliably invoke the downstream job.
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
[JIRA] (JENKINS-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott commented on JENKINS-38850 Re: Multijob runs one parameterized child job instead of running multiple child jobs with different parameters I'm "glad" someone else experienced this too... Configuration: Jenkins 2.19.4 Multijob Plugin 1.21 EnvInject Plugin 1.93.1 Token Macro Plugin 2.0 Parameterized Trigger Plugin 2.32 Six weeks ago we updated some plugins, including Multijob Plugin 1.21 => 1.23. Since then we started missing job builds. Today I rolled back only the Multijob Plugin 1.23 => 1.21, and the issue dissapeared. I've assembled some test jobs and have let , with following structure where the ~worker job can run in parallel. The ~X1 .. ~X5 jobs invoke the ~worker job with different parameters, that's 100% sure (see attached XML job configuration files). With Multijob Plugin 1.23 some (up to all) ~worker invocations are merged, and the resulting build receives the parameters of one of the merged invocations, here an example: As Joan Roch already noted, the problem occurs only if the build number (ID) of the upstream jobs ~X1 .. ~X5 is the same. If you start one of the upstream jobs few times separately, thus increasing its "next build number" to a number != to the other build numbers, that upstream job will reliably invoke the downstream job. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-38850 Multijob runs one parameterized child job instead of running multiple child jobs with different parameters Change By: Victor Ott Attachment: ~worker-config.xml 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-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-38850 Multijob runs one parameterized child job instead of running multiple child jobs with different parameters Change By: Victor Ott Attachment: ~X1-to-X5-config.xml 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-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-38850 Multijob runs one parameterized child job instead of running multiple child jobs with different parameters Change By: Victor Ott Attachment: ~X-config.xml 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-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-38850 Multijob runs one parameterized child job instead of running multiple child jobs with different parameters Change By: Victor Ott Attachment: job-builds-merged.png 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-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-38850 Multijob runs one parameterized child job instead of running multiple child jobs with different parameters Change By: Victor Ott Attachment: multijob-structure.png 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-20311) Multi Job Plugin should be able to create multiple instances of a parametrized build
Title: Message Title Victor Ott commented on JENKINS-20311 Re: Multi Job Plugin should be able to create multiple instances of a parametrized build @Rahul Somasunderam Please could you elaborate why you are not able to add multiple invocations of the parameterized job to the multijob job? I can't see any obstacles for that, and it works for me. Do you receive any error messages or ... ? 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-20515) Parammertized jobs re evaluate parent multijob's Parameters
Title: Message Title Victor Ott commented on JENKINS-20515 Re: Parammertized jobs re evaluate parent multijob's Parameters @Lior Boord Is this issue report still valid? I am not able to reproduce this issue with following environment: Jenkins 2.19.4 Multijob Plugin 1.21 EnvInject Plugin 1.93.1 Token Macro Plugin 2.0 Parameterized Trigger Plugin 2.32 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-31097) invoking multiple instances of a parameterized build job from a workflow results in downstream job getting run once
Title: Message Title
Victor Ott updated an issue
Jenkins / JENKINS-31097
invoking multiple instances of a parameterized build job from a workflow results in downstream job getting run once
Change By:
Victor Ott
I'm attempting to have a workflow dynamically construct the branch map to pass to parallel to invoke a single parameterized downstream job multiple times with different sets of parameters. If I define the branches map statically, it can invoke multiple instances of the parameterized job as expected (it gets run multiple times, and each has its expected, different set of parameters). If I try to construct that barnches map dynamically in the workflow, the result is the downstream job getting run once with one of those sets of parameters, though it reports that it was invoked twice by the upstream workflow job.Here's the static definition that works as expected: {code:java} def nodes = [:]nodes['alpha'] = ['OPT': 'alpha',]nodes['beta'] = ['OPT': 'beta',]def paramList (param, val) {List ret = []ret += new hudson.model.StringParameterValue(param, val)return ret}def paramnodes = [:]paramnodes['alpha'] = {node() {build job: 'parameterized-build-job', parameters: paramList('nodename', 'alpha')}}paramnodes['beta'] = {node() {build job: 'parameterized-build-job', parameters: paramList('nodename', 'beta')}}parallel paramnodes {code} And here's the dynamic construction that behaves oddly: {code:java} def nodes = [:]nodes['alpha'] = ['OPT': 'alpha',]nodes['beta'] = ['OPT': 'beta',]def paramList (param, val) {List ret = []ret += new hudson.model.StringParameterValue(param, val)return ret}def nodelist = ['alpha', 'beta']def paramnodes = [:]def nodename = nullfor (int i = 0; i < nodelist.size(); i++) {nodename = nodelist[i]paramnodes[nodename] = {node() {build job: 'parameterized-build-job', parameters: paramList('nodename', nodename)}}}parallel paramnodes {code} (I was trying to define nodelist with a much more useful "def nodelist = nodes.keySet().toList()" but changed it to a statically defined list in this example just to remove keySet() being nonserializable from consideration)
Add Comment
[JIRA] (JENKINS-39268) Properties are not passed to Maven command by Maven build step
Title: Message Title Victor Ott commented on JENKINS-39268 Re: Properties are not passed to Maven command by Maven build step Submitted pull request: https://github.com/jenkinsci/jenkins/pull/2638 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 build step
Title: Message Title Victor Ott assigned an issue to Victor Ott Jenkins / JENKINS-39268 Properties are not passed to Maven command by Maven build step Change By: Victor Ott Assignee: Victor Ott 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 build step
Title: Message Title Victor Ott started work on JENKINS-39268 Change By: Victor Ott Status: Open In Progress 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 build step
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-39268 Properties are not passed to Maven command by Maven build step Change By: Victor Ott Summary: Properties are not passed to Maven command by Maven task build step 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 task
Title: Message Title
Victor Ott updated an issue
Jenkins / JENKINS-39268
Properties are not passed to Maven command by Maven task
Change By:
Victor Ott
The command I'm trying to get jenkins to execute is like this:{code}mvn -Dparam1=val1 -Dparam2=val2 -f bdd/pom.xml test{code}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 in a "{{Invoke top-level Maven targets}}" build step, 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.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39268) Properties are not passed to Maven command by Maven task
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-39268 Properties are not passed to Maven command by Maven task Change By: Victor Ott Summary: Properties are not passed to maven Maven command by maven integration plugin Maven task 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
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.
