Hi Edin,

I also got the similar scenario. We usually receive some installer file 
from developers and which we require to copy on multiple *windows* servers 
in different environments(ex: QA,STAGE etc) and run that installer using 
PowerShell on each server. 
1. I am running my Master Jenkins on Linux machine and installed a 
Jenkins-Slave on one of the Windows QA server.
2. Now I am able to execute any PowerShell command from Jenkins to the the 
windows slave machine.

Need to do:

1. Now I want to copy the file(which we receive from developers in a 
ticket) to all of the Windows server and execute that in PowerShell.

May you please advise me how can I copy this file on all of the servers and 
execute? I'd really appreciate any help on this.

Thanks and Regards.
Nitesh


On Tuesday, December 3, 2013 at 4:14:24 PM UTC+5:30, Edin wrote:
>
> Thank you, Eric (sorry for the late reply).
>
> We create the installation files in our build pipeline and then publish 
> these to an artifact repository ("outside" Jenkins) so the Copy Artifact 
> plugin could be used but would the require us to first copy the 
> installation files back to the workspace of the deployment job which is 
> time consuming.
>
> In the end we decided to solve this by performing a network file copy from 
> the artifact repository directly to the server that is deployed. By 
> executing a PowerShell script locally (Jenkins agents on the servers) in 
> our deployment job and then starts the actual installation.
>
> Best regards,
> Edin
>
> Den måndagen den 4:e november 2013 kl. 17:06:13 UTC+1 skrev Eric Pyle:
>>
>> Hi, 
>>
>> If the installation files are also created by a Jenkins job, you can 
>> have the job save them as artifacts, and then use the Copy Artifact 
>> Plugin on your test/prod jobs to retrieve the files. 
>>
>> Cheers, 
>> Eric 
>>
>> On 11/4/2013 10:59 AM, Edin Mujkanovic wrote: 
>> > 
>> > Hi! 
>> > 
>> > We are currently creating a job in Jenkins, that will be used to 
>> > deploy the system we are developing, to various test and production 
>> > server environments (~40 servers in total, where each environment 
>> > consist of 4 servers with different roles)). 
>> > 
>> > Our main concern now is that the job needs to copy the installation 
>> > files to each server from a central file repository (currently a file 
>> > share on the buildserver) and then perform the installation by 
>> > executing one of these files locally on the server. 
>> > During installation several windows services and IIS webapplications 
>> > are (re)installed. 
>> > 
>> > Currently we are leaning towards running Jenkins slaves on the 
>> > test/prod servers: 
>> > It would be nice if we could copy the files using the Jenkins slave 
>> > agent and not having to mount/refer to the central repository file 
>> > share from each server. 
>> > 
>> > Are there any good methods in conjunction with plugins to solve this 
>> > in a efficient and secure way? 
>> > 
>> > Our environment: 
>> > -Jenkins 1.528 
>> > -Build scripts in NAnt 
>> > -Windows Server 2008 R2 
>> > -Ideally we would like to be able to perform test deploys of the 
>> > system on our individual development workstations, which currently run 
>> > Windows 7 Enterprise edition. 
>> > 
>> > I'm grateful to hear your thoughts about this. 
>> > 
>> > Best regards, 
>> > Edin 
>> > 
>> > -- 
>> > 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-use...@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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a3ffd66e-a44f-47b0-974a-2c326a8a3f75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to