Hello I wonder if anyone can help me as I have a problem with my Jenkins install caused by a change in our corporate AV policy.
We have a Build server, that lives on Domain A, and we have a system test environment that lives on Domain B. At the moment the Build server does the build and then triggers some deployment steps to roll out the MSI installer packages and execute them on the machines in domain B. This is done using PSEXEC to run the command on the remote servers in domain B. Since the recent Petya oubreak and other ransom ware, our AV now has a rule that is stopping all access to PSEXEC. Causing our automated deployments to system test to fail. What I am trying to work out is if there is a better way to trigger the deployments to happen so that we don't need to use PSEXEC at all. The deployment packages really need to be MSI as they are manually moved into the production environments due to security concerns and we need to maximise the automation. Any suggestions, pointers welcomed. Thanks Ben -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/26585e19-8784-410c-bae7-431effcd74f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
