arameter pluging from a declarative
> pipeline (
> https://wiki.jenkins.io/display/JENKINS/NodeLabel+Parameter+Plugin).
> Anyone have any ideas how to make this work ? It seems like the
> NodeParameter isnt even available in declarative pipelines ?
>
>
>
> --
> You re
Im trying to use the NodeLabel Parameter pluging from a declarative
pipeline
(https://wiki.jenkins.io/display/JENKINS/NodeLabel+Parameter+Plugin).
Anyone have any ideas how to make this work ? It seems like the
NodeParameter isnt even available in declarative pipelines ?
--
You received
For prosperity, my finding is:
1. it seem like the node have their node name as label automatically (I
realized this when trying to add the node name to the label, the label was
disappearing when saving the changes)
2. Knowning number 1 point, I could just use the named parametrized
Is anybody can point me to some info or an how to use the node and label
parameter.
I can make it work with a choice list but I would rather make it work with
the plugin if possible with proper default value.
--
You received this message because you are subscribed to the Google Groups
"Jenkin
Hi,
It turns out that the NodeLabel Parameter plugin doesn't work with the
workflow plugin:
https://issues.jenkins-ci.org/browse/JENKINS-32209
I submitted this fix:
https://github.com/jenkinsci/nodelabelparameter-plugin/pull/10
--
Craig
On Tue, Dec 22, 2015 at 4:41 PM, Craig Rodrigues
Hi,
Can someone provide some workflow groovy which takes
a "Node Parameter" from the NodeLabel Parameter plugin,
and then uses it in a workflow script?
I couldn't figure out how to do it, and kept getting null exceptions
when I tried to use the parameter.
--
Craig
--
You receiv
I have two nodes defined with the same label.
NodeA (label mygit)
NodeB (label mygit)
I am using the build flow plugin and have a script that gets called from
the main build job that performs the following
build(joba.sh)
parallel{
{build (jobb.sh),
build (jobc.sh),
build (jobd.sh
I have a build flow plugin configuration for my build job in
jenkins(main-build-job). I want to make sure that my build occurs on
one of two machines so I installed the nodelabel parameter plugin. My
build flow is
build ("joba.sh", PARENT_BUILD_ID :
build.properties.e
I solve it creating the job like "multi-configuration job".
Then, just configured the job normally and under "Configuration Matrix",
"Node/Label" selected all the nodes where I want the job to run.
And its done.
Quinta-feira, 1 de Agosto de 2013 15:39:33 UTC+1, Tânia Magalhães escreveu:
>
> Tha
That way I won't have the job build in each node, but only in one of the
possible nodes (the ones with that label...).
I will try with multi-configuration job.
Thanks.
Quinta-feira, 1 de Agosto de 2013 15:28:37 UTC+1, Steffen escreveu:
>
> > Just add a label on the slaves that you want to run
> Just add a label on the slaves that you want to run your job on and
> then
> add the label to your job configuration under "Restrict where this
> project can be run".
This is, by the way, achieved without any plugins.
--
You received this message because you are subscribed to the Google Group
Hi Tânia!
On Thu, 2013-08-01 at 07:09 -0700, Tânia Magalhães wrote:
> Does anyone knows how to this with this plugin or in other way?
Just add a label on the slaves that you want to run your job on and then
add the label to your job configuration under "Restrict where this
project can be run".
R
/NodeLabel+Parameter+Plugin
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https
13 matches
Mail list logo
