[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title Karolina Arancibia Valuskova updated an issue Jenkins / JENKINS-59431 When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node Change By: Karolina Arancibia Valuskova Component/s: parameterized-trigger-plugin Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202015.1568813775000.6453.1578666781051%40Atlassian.JIRA.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title Karolina Arancibia Valuskova updated an issue Jenkins / JENKINS-59431 When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node Change By: Karolina Arancibia Valuskova Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202015.1568813775000.6455.1578666781160%40Atlassian.JIRA.
[JIRA] (JENKINS-60732) Node is repeated in execution
Title: Message Title Karolina Arancibia Valuskova created an issue Jenkins / JENKINS-60732 Node is repeated in execution Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin, parameterized-trigger-plugin Created: 2020-01-10 14:31 Labels: nodelabelparameter parameterized-trigger Priority: Blocker Reporter: Karolina Arancibia Valuskova When using All Nodes For Label Factory, the nodes in the execution are detected correctly (per log under job//build#) but the nodes that the triggered job actually runs in are not right, and a Node is used more than once (usually the first discovered). Add Comment
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title Karolina Arancibia Valuskova updated an issue Jenkins / JENKINS-59431 When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node Change By: Karolina Arancibia Valuskova Comment: There is a similar problem when there are two groups of nodes : 6 nodes with TESTPC label and 6 nodes with PRODPC label. The plugin would send the run call to all of them regardless of the label they have, this is a big issue of broken functionality. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202015.1568813775000.6406.1578664860589%40Atlassian.JIRA.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title
Karolina Arancibia Valuskova updated an issue
Jenkins / JENKINS-59431
When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Change By:
Karolina Arancibia Valuskova
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes.{{I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists.}}{{-The same applies when I have groups of different nodes with a single label. }}{{-There is the same problem with the Node - Factory part of the plugin.}}{{Here is the log of a build that should have run on TESTPC1,2 and 3, but instead run on TESPC 5 (twice) and PRODPC6 (PC with different label)}}{code:java}Started by user [8mha:4GcLNmTz8oi6tKjMMjxnTRRbUCKLrip2lyOZlKIRHdypmx+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyuEgZ+/dLi1CL94syUktTiktQiAKFXgYvE [0m Running as SYSTEM Building remotely on [8mha:4JNmtgR2g18637CcH5OrJjPvakAXl1al6Pij6HjPxIbMnR+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZB/eT83ILSktQi/WBnR78AZzMAOdpwt8Y= [0mTESTPC6 (TESTPC) in workspace C:/jenkins/workspace/ define: [LabelParameterValue: NODELABEL=TESTPC1] define: [LabelParameterValue: NODELABEL=TESTPC2] define: [LabelParameterValue: NODELABEL=TESTPC3] Triggering projects: [8mha:4GEYBZuNUHdwWOzB3SOyspk29pTLutRnS9YcoIxnTpKWlx+LCP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMgQKGEQ08/KT9J3zSvLLMrPy03NKwlOLSkt0AcArVNUhJs= [0mFinished: SUCCESS{code}Which seems to indicate that the job was send to build before the nodes were selected.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title
Karolina Arancibia Valuskova updated an issue
Jenkins / JENKINS-59431
When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Change By:
Karolina Arancibia Valuskova
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes.{{I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists.}}{{-The same applies when I have groups of different nodes with a single label. i.e. 12 nodes 6 with TESTPC and 6 with PRODPC }} {{-There is the same problem with the Node - Factory part of the plugin.}}{{Here is the log of a build that should have run on TESTPC1,2 and 3, but instead run on TESPC 5 (twice) and PRODPC6 (PC with different label)}}{code:java}Started by user [8mha:4GcLNmTz8oi6tKjMMjxnTRRbUCKLrip2lyOZlKIRHdypmx+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyuEgZ+/dLi1CL94syUktTiktQiAKFXgYvE [0m Running as SYSTEM Building remotely on [8mha:4JNmtgR2g18637CcH5OrJjPvakAXl1al6Pij6HjPxIbMnR+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZB/eT83ILSktQi/WBnR78AZzMAOdpwt8Y= [0mTESTPC6 (TESTPC) in workspace C:/jenkins/workspace/ define: [LabelParameterValue: NODELABEL=TESTPC1] define: [LabelParameterValue: NODELABEL=TESTPC2] define: [LabelParameterValue: NODELABEL=TESTPC3] Triggering projects: [8mha:4GEYBZuNUHdwWOzB3SOyspk29pTLutRnS9YcoIxnTpKWlx+LCP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMgQKGEQ08/KT9J3zSvLLMrPy03NKwlOLSkt0AcArVNUhJs= [0mFinished: SUCCESS{code}Which seems to indicate that the job was send to build before the nodes were selected.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title
Karolina Arancibia Valuskova updated an issue
Jenkins / JENKINS-59431
When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Change By:
Karolina Arancibia Valuskova
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes. {{ I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists. }}{{-The same applies when I have groups of different nodes with a single label. }}{{-There is the same problem with the Node - Factory part of the plugin.}}{{Here is the log of a build that should have run on TESTPC1,2 and 3, but instead run on TESPC 5 (twice) and PRODPC6 (PC with different label)}}{code:java}Started by user [8mha:4GcLNmTz8oi6tKjMMjxnTRRbUCKLrip2lyOZlKIRHdypmx+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyuEgZ+/dLi1CL94syUktTiktQiAKFXgYvE [0m Running as SYSTEM Building remotely on [8mha:4JNmtgR2g18637CcH5OrJjPvakAXl1al6Pij6HjPxIbMnR+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZB/eT83ILSktQi/WBnR78AZzMAOdpwt8Y= [0mTESTPC6 (TESTPC) in workspace C:/jenkins/workspace/ define: [LabelParameterValue: NODELABEL=TESTPC1] define: [LabelParameterValue: NODELABEL=TESTPC2] define: [LabelParameterValue: NODELABEL=TESTPC3] Triggering projects: [8mha:4GEYBZuNUHdwWOzB3SOyspk29pTLutRnS9YcoIxnTpKWlx+LCP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMgQKGEQ08/KT9J3zSvLLMrPy03NKwlOLSkt0AcArVNUhJs= [0mFinished: SUCCESS{code}Which seems to indicate that the job was send to build before the nodes were selected.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-59431 Re: When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node There is a similar problem when there are two groups of nodes : 6 nodes with TESTPC label and 6 nodes with PRODPC label. The plugin would send the run call to all of them regardless of the label they have, this is a big issue of broken functionality. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202015.1568813775000.6389.1578659700107%40Atlassian.JIRA.
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title
Karolina Arancibia Valuskova commented on JENKINS-43820
Re: Stage name must be a string literal
This worked for me (Jenkins ver 2.190.1): stage ("Deploy ${BRANCH_NAME}")
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.3289.1570535940873%40Atlassian.JIRA.
[JIRA] (JENKINS-58833) NodeLabel Parameter Plugin does not work for concurrent
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-58833 Re: NodeLabel Parameter Plugin does not work for concurrent I have also run into this issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201147.1565117754000.3922.1569314340167%40Atlassian.JIRA.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title
Karolina Arancibia Valuskova created an issue
Jenkins / JENKINS-59431
When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
nodelabelparameter-plugin
Created:
2019-09-18 13:36
Environment:
Jenkins ver 2.176.3 Node and Label parameter plugin ver. 1.7.2 Parametrized Trigger plugin ver 2.35.2
Labels:
nodelabelparameter
Priority:
Major
Reporter:
Karolina Arancibia Valuskova
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes. I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-39219 Re: Pipeline from SCM options disappear tal z no, as a work around I change the pipeline > definition to: **pipeline script. Save. Then change again to pipeline script from SCM, and then the SCM options are back. it is a bit of a pain, but since we are planning to use a repository in the future, it is not a big issue for us. Hope that helps until this is fixed. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175646.1477332308000.15160.1563442440189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-39219 Re: Pipeline from SCM options disappear was this actually solved? I run into the same issue in version 2.176.1 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175646.1477332308000.2236.1562317680160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42216) Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config
Title: Message Title Karolina Arancibia Valuskova edited a comment on JENKINS-42216 Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue.This is blocking the build of the job, since it throws a NP Null Pointer when it tries to find the scm even though I specified it as 'None' 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179104.148768634.2229.1562317500193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42216) Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config
Title: Message Title Karolina Arancibia Valuskova edited a comment on JENKINS-42216 Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue. This is blocking the build of the job, since it throws a NP when it tries to find the scm 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179104.148768634.2220.1562317440265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42216) Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-42216 Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179104.148768634.2217.1562317320785%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
