[JIRA] (JENKINS-47724) Pipeline with parallel jobs performance issue with EC2 slaves
Title: Message Title Jan Bottek commented on JENKINS-47724 Re: Pipeline with parallel jobs performance issue with EC2 slaves Hi, we are running in the same limitation that paralle is slowing down with the number of parallel steps we have. we tried all the solutions from above, but none of these helped - as Mike Kozell also mentioned. The recommended solution to use Parallel Test Executor Plugin is not working for us, because for that i have to know how many executors are available during the creation of the parallel testGroups. But normally i would provide a NODE label and if any new node is available it will grab some work from the queue - this will not longer working with Parallel Test Executor Plugin - or i am wrong? thx in advance. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud Hi Michel, now i got it. I only change the SSH User for template 2 instead of changing it on template one for validation. Thanks for help. So hope this workaround helps to find the bug. 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-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud I now deleted also my second Cloud Instance and configured a second template to my first Cloud instance, but same result, i cannot get the workaround working. Any idea what is different between our two setups? 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-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud Hi, yes saved the settings, but same results. Currently i worked around this bug with a second Cloud Instance. 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-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud Hi Michael, the workaround you provided didn't worked for me. I changed the Launch Method the SSH and select the credentials which i already select for the Vsphere host, instead the one i have to use really for SSH connection. But i get the same error before. 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-34389) starting parallel matrix jobs with dynamic axes causes in wrong build configuration
Title: Message Title Jan Bottek commented on JENKINS-34389 Re: starting parallel matrix jobs with dynamic axes causes in wrong build configuration Hi all, something new about this issue? Can i help by giving more analyze information? Thanks in advance Kind regards Jan 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-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek created an issue Jenkins / JENKINS-40336 invalid login for second template in one vsphere cloud Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2016/Dec/09 1:26 PM Environment: Jenkins 2.19.1 Vsphere Plugin 2.14 Vsphere Server 5.5 Windows Server 2008 R2 Labels: plugin jenkins vsphere Priority: Major Reporter: Jan Bottek if i create a Vsphere Cloud and one template => check template is working fine. If i then duplicate the template entry and try "check template" on the second, i get the following error message Problem validating org.jenkinsci.plugins.vsphere.tools.VSphereException: com.vmware.vim25.InvalidLogin: The logon can not be completed due to an incorrect user name or password If i create another Vsphere Cloud and one template their, it is also working, only the second template is not working.
[JIRA] [dynamic-axis-plugin] (JENKINS-34389) starting parallel matrix jobs with dynamic axes causes in wrong build configuration
Title: Message Title Jan Bottek commented on JENKINS-34389 Re: starting parallel matrix jobs with dynamic axes causes in wrong build configuration addendum: i thin this issue is similar to JENKINS-30437 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [dynamic-axis-plugin] (JENKINS-34389) starting parallel matrix jobs with dynamic axes causes in wrong build configuration
Title: Message Title Jan Bottek created an issue Jenkins / JENKINS-34389 starting parallel matrix jobs with dynamic axes causes in wrong build configuration Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: jobs.zip Components: dynamic-axis-plugin, matrix-project-plugin Created: 2016/Apr/22 6:54 AM Environment: Jenkins: 1.609/1.650 Windows Dynamic Axis: 1.0.3 Matrix Project: 1.6 Labels: plugin matrix jenkins dynamic-axis Priority: Major Reporter: Jan Bottek We create a matrix project which gets its dynamic axes from build parameter. The job is doeing nothing instead printing some messages and wait an amount of time. Now we create an upstream project. This project calls the matrix project with different axis as a build
[JIRA] [dynamic-axis-plugin] (JENKINS-30437) Build status page displays incorrect run combinaison for matrix build with dynamic axis
Title: Message Title Jan Bottek commented on JENKINS-30437 Re: Build status page displays incorrect run combinaison for matrix build with dynamic axis Hi, we patched the plugin on our local server with the bugfix mentioned above. With the fix we had much less incorrect links, but sometimes the problem still occurs - till now we didn't find a reproducible way to solve it and always get correct links. I there any updates, or someone has a idea? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
