15
votes

We're using Jenkins on Win8 x64 to build (msbuild), package (cspack), run (csrun) and test (nunit) an azure cloud services project. The Azure cloud service emulators need to run as administrator plus we need to bind to ports 80/443 (so can't use "lite" emulators).

We're doing the above via a simple .bat file that Jenkins runs. Typically no user logs into the machine, it boots up and Jenkin's runs as a service that keeps monitoring our GIT repo and emails on failures. An admin manually logs into the machine just for maintenance (eg. apply patches or reboot machine etc)

How do we configure Jenkins to run that .bat as administrator without human interaction?

With a desktop UI we can right click a command prompt, run as admin, acknowledge the UAC prompt, get the elevated privilege prompt and run the .bat file.

4

4 Answers

23
votes

Our solution was to run the Jenkins' service as a separate local admin user. After installing Jenkins, Start => 'services' => Scroll to the Jenkins service => right click => properties => "log on" => "this account" => specify a local admin account.

Hopefully in newer Jenkins' builds it can work as the standard NETWORK SERVICE but for some reason it didn't with our box.

5
votes

One of the solution:

  1. Create bat file in slave.
  2. Create shortcut of the file and right click the shortcut, properties -> Advanced -> check run as administrator.
  3. Control Panel -> System and Security -> Action Center -> Change User Account Control Settings and set the level to "never notify".
  4. run the file on Jenkins

Somehow the file will be executed on slave server but it return failure on Jenkins.

2
votes

This is My situation:

I need to use admin privileged console to run pywinauto script (written in python) to automate some app which requires admin privileged.

What I had tried:

  1. In my experience, install Windows Jenkins slave as a service creating more issue to take care with, so I don't go this route.
  2. To create a new process and it will open a new admin privileged shell and run command on it. But, in this way, Jenkins will not show its output, say in Blue Ocean.

What worked for me:

  1. Just manually open an admin privileged console to start the your_window_node.jnlp file and then this Jenkins slave will have admin privileged.
0
votes

If you'll log to the widows machine as an administrator and run the slave agent from this user, everything will be running under the administrator user