Le 26 sept. 2013 19:01, "Tânia Magalhães" <taniamagalh...@gmail.com> a écrit : > > Yes, of course there is a logic behind my needs... > I just think that it is useless explain the all process here.
That point is actually far more important than you seem to think. Not sure you have to explain everything, sure, but you generally should explain at least some of the things in a preferably concise manner, when you ask for help. In fact, people here are human and volunteers, so there's you should try to convince people you're not doing something stupid/weird (not saying you're doing right here, just speaking for the general case), because most helpers would be logically reluctant to help another doing something they think should *not* be done. Even more as time is limited, they'll just carry on to the next question in this kind of case. > > What I need is what I described above. > Any ideas? > So far I was not able to do it... > > To remind, I am running jenkins on windows. > Thanks. > > > Terça-feira, 24 de Setembro de 2013 19:26:50 UTC+1, LesMikesell escreveu: >> >> On Tue, Sep 24, 2013 at 11:52 AM, Tânia Magalhães >> <taniama...@gmail.com> wrote: >> > Until now I was doing like that, having a label to identify my main_slave. >> > >> > But then we had the need to add a build step that copy some files from >> > main_slave to other slaves. We are doing this via "Execute windows batch >> > command" and the command lines were first something like: xcopy >> > \\main_slave_name\c$\tmp C:\tmp /E /I /Y >> > >> > To avoid the need of having to change those command lines to copy from the >> > correct main slave, we create a global property named MAIN_SLAVE. Now we >> > just need to do: xcopy \\%MAIN_SLAVE%\c$\tmp C:\tmp /E /I /Y >> > This way we do not have to care anymore to change all the command lines like >> > that, we just need to change the value for our global property named >> > MAIN_SLAVE. >> > >> > Since we have that global property and since we still have to deal with >> > forcing some jobs to run at main slave, even if we just have to delete the >> > label main_slave from one slave and add it to another, it woul be much >> > better if we can deal both problems on the same way, and to me it seems >> > clear that using global properties would be the best choice. All I need is >> > to find a way to use global properties values at "restrict where..." >> >> I still don't understand the concept of one slave needing to be 'main' >> or even it that is so, why it ever needs to change, so the whole >> concept doesn't make much sense to me and my recommendation is still >> to generalize the way you handle the build results so no single slave >> is special (i.e. archive the artifacts and use the copy artifact >> plugin to get them where you need them next, drop them on a common >> network share, commit to some common repository, etc.).. >> >> But, if there is some logic behind the sequence of events you need, >> maybe you could use the rest api to trigger a parameterized build with >> the node being passed as a parameter - perhaps you already have some >> program that understands or controls the state of things. >> >> -- >> Les Mikesell >> lesmi...@gmail.com > > -- > 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://groups.google.com/groups/opt_out. -- 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://groups.google.com/groups/opt_out.
