Re: Running a jenkins windows batch command non-headless mode

2014-05-01 Thread Mark Mikulec
Nope, even when I'm logged on, it doesn't work. However I stopped the service and ran it directly via the command line. That in fact did work. A bit sloppy, but that's just the way windows is. Thanks for everyone's help! bc On May 1, 2014 11:07 AM, "Mark Mikulec"

Re: Running a jenkins windows batch command non-headless mode

2014-05-01 Thread Mark Mikulec
count instead of local system? >> >> As I said, you could set up a slave service to run on this machine for >> certain jobs and have that be under local system. >> >> -- >> *From: *"Mark Mikulec" >> *To: *jenkinsci-

Re: Running a jenkins windows batch command non-headless mode

2014-05-01 Thread Mark Mikulec
gt; account instead of local system? > > As I said, you could set up a slave service to run on this machine for > certain jobs and have that be under local system. > > ------ > *From: *"Mark Mikulec" > *To: *jenkinsci-users@googlegroups.com

Re: Running a jenkins windows batch command non-headless mode

2014-05-01 Thread Mark Mikulec
Since I'm using already a custom Jenkins local account, I do not have that option. Which is why I'm confused that it doesn't work. Maybe its because its a service? On May 1, 2014 8:31 AM, wrote: > Yeah you should be able to install the slave as a service > Go into services, right click on the sla

Re: Running a jenkins windows batch command non-headless mode

2014-05-01 Thread Mark Mikulec
This is my main Jenkins box though. How will this affect all my other jobs? On May 1, 2014 8:31 AM, wrote: > Yeah you should be able to install the slave as a service > Go into services, right click on the slave service and go to properties > Go to the "Log On" tab and check the box that says "Al

Re: Upgrade from 1.472 to 1.541 failing

2013-12-03 Thread Mark Mikulec
ink the developers > would like to know you're setup that failed upgrade. However, they need you > to narrow the cause of the upgrade failure and that usually takes time and > experimentation > > > > Mark > > > > On Dec 3, 2013 12:22 PM, "Mark Mikulec"

Re: Upgrade from 1.472 to 1.541 failing

2013-12-03 Thread Mark Mikulec
Hi Mark, Thanks for the tip - that build worked flawlessly! Mark __ Learn more about.me . On 2 December 2013 13:48, Mark Waite wrote: > If you were running a version of Jenkins for that long without upgrading, > you