Thanks a lot Mark for your quick response! As I understand it the goal is to create a slave/agent that will run the code signing directly on windows, instead of a service. great idea!
However, I am stuck at step 4, I dond't see the "Launch agent via Java Web Start" option. I found a general solution online <https://stackoverflow.com/questions/40340097/there-is-no-launch-agent-via-java-web-start-option-in-my-jenkins-when-i-adding>, by specifying a concrete or random port in the Global Security TCP settings. I tried both, and even restarted Jenkins a couple of times, and it doesn't show up. I only see 1) Launch agent by connecting it to the master, 2) ... via execution of command on the master, 3) ... Let Jenkins control this Windows slave as a Windows service. Also checked if there are any updates of Jenkins, only some unrelated plugin-updates are available. Anything else I could check? Thank you! Am Mittwoch, 8. Mai 2019 16:05:00 UTC+2 schrieb Mark Waite: > > > > On Wednesday, May 8, 2019 at 7:18:31 AM UTC-6, A M wrote: >> >> hi Mark >> >> I am struggling with a very similar issue. What exactly do you mean by >> your comment and how do I achieve this? >> >> > I said: > > > Run the Windows agent from the Windows desktop rather than running it > from a service which has been allowed to interact with the desktop. > > The most direct way to implement what I described is to: > > 1. Login to the Windows desktop machine where code signing will be run > 2. Open a web browser to the Jenkins server > 3. Create an agent (a node) to represent that Windows computer > 4. Configure the agent to "Launch agent via Java Web Start" > 5. Define the required agent fields (like a remote root directory - I > prefer 'C:\J\' to reduce problems with Windows and long paths) and save > the > configuration of that agent > 6. Download the 'agent.jar' file from the hyperlink on the web page, > save it somewhere convenient (like C:\J\agent.jar) > 7. Open a command prompt window on the Windows desktop machine and > change to the convenient directory C:\J > 8. Copy the 'Run from agent command line" from the web page into the > command prompt window > > Thanks for asking! > Mark Waite > > >> I want to run the signtool.exe together with the certificate on a USB >> token as an AfterPublish job in Jenkins. Jenkins is running as admin. >> Single sign-on is activated for the USB token. Running signtool.exe in the >> admin console works, running the same command through Jenkins results in >> the "No certificates were found that met all the given criteria." error. >> >> Any help is much appreciated. Thank you! >>> >>> -- 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/b92c3356-23da-4368-b6b7-a5fd2906e110%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
