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 L
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 o
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
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
