[JIRA] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Christopher Orr resolved JENKINS-12998 as Won't Fix Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ As noted, there are defined extension points in core for this and plugins which implement them, so this won't be reimplemented in core. Change By: Christopher Orr (19/Mar/15 3:24 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Miroslav Nedyalkov commented on JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ Daniel, thanks for the information. I guess we should stick to one of the plugins for the time being This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Daniel Beck
edited a comment on JENKINS-12998
Allows variable subistution for Job 'Restrict where this project can be run' label _expression_
Miroslav: The other issue was marked resolved because plugins solve it.
It seems in this one users insist it be a core feature, despite extension points existing that support this and multiple plugins implementing those.
Indeed as a general UX thing I first expected that I could use a ${parameter} anywhere that I could type text and was disappointed to find only some things supported it and some of those only seem to support it on the server-side whilst telling you it's invalid in the UI
There will never be full support for variable replacement because it's specifically set up to be optional for any configuration options. So while it could be added to the label _expression_ (in theory), it will not be the first step to unifying the behavior of everything.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Daniel Beck commented on JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ Miroslav: The other issue was marked resolved because plugins solve it. It seems in this one users insist it be a core feature, despite extension points existing that support this and multiple plugins implementing those. I'm using nodelabel for this but can see why this should be core functionality as it was a let down to find this out There will never be full support for variable replacement because it's specifically set up to be optional for any configuration options. So while it could be added to the label _expression_ (in theory), it will not be the first step to unifying the behavior of everything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Miroslav Nedyalkov commented on JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ The same problem seems to be logged already here - https://issues.jenkins-ci.org/browse/JENKINS-9665. It also states to be resolved, so I guess this one is also done. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Victor Lopez edited a comment on JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ I'm having the same issue here.. I have several nodes that can run a job, and I want to be able to specify through parameters whether it should be run by one specific node or that it doesn't matter which node runs it. I am trying to do it by assigning the label "any" to all the nodes, the job has a choice parameter containing all the node names plus the label "any", if the parameter is "any" all the nodes can execute this job. Nodelabel plugin doesn't allow me to do it, because it forces me to pick a node, and I cannot have the option to run it in any available node. edit: The situation I described above can be done with a Label paremeter from the NodeLabel plugin. It cannot display the node names and labels as a choice list, but they can be entered manually. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Victor Lopez commented on JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ I'm having the same issue here.. I have several nodes that can run a job, and I want to be able to specify through parameters whether it should be run by one specific node or that it doesn't matter which node runs it. I am trying to do it by assigning the label "any" to all the nodes, the job has a choice parameter containing all the node names plus the label "any", if the parameter is "any" all the nodes can execute this job. Nodelabel plugin doesn't allow me to do it, because it forces me to pick a node, and I cannot have the option to run it in any available node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Daniel Beck updated JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ Change By: Daniel Beck (29/Jun/14 5:29 PM) Labels: labels This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Marc Carter
commented on JENKINS-12998
Allows variable subistution for Job 'Restrict where this project can be run' label _expression_
I'm using nodelabel for this but can see why this should be core functionality as it was a let down to find this out . The fact that nodelabel specifically competes with (rather than extends) the existing constraint system should be enough to tell you that something is "missing".
Indeed as a general UX thing I first expected that I could use a ${parameter} anywhere that I could type text and was disappointed to find only some things supported it and some of those only seem to support it on the server-side whilst telling you it's invalid in the UI.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Daniel Beck commented on JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ Doesn't the NodeLabel Parameter plugin do the job? What's the rationale to request inclusion in core? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Ryan Small commented on JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ +1 I would love to pass a parameter from one job to the next, and assign that parameter value to a node label variable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
