On Thursday, April 19, 2012 at 5:13:30 PM UTC+5:30, Lee Winder wrote:
>
> I have a single batch file which calls a number of executables which
> builds various assets for our application. When I run the batch file
> manually it works perfectly (the command prompt opens, the assets are built
>
Hi,
I too faced same problem.
I tried runas .
Also tried with variuos options of CMD in x32 and x64.
I am nost sure about actual casuse but I observed that My Jenkins was
installed in x32
C:\Program Files (x86)\Jenkins\jobs\
> > > > > Build\workspace
> > > C:\Windows\TEMP\jenkins233398854
Hi Lee,
I am not sure if you are active in this group still but just giving a try.
Can you please explain in detail what u did exactly?
On Thursday, May 17, 2012 at 2:06:43 PM UTC+5:30, Lee Winder wrote:
>
> Hi Indyn
>
> I solved my problem by moving the executable calls outside of the build
> p
Hi folks,
runas has an option called /savecred. You would have to use runas once in
the wanted user context and enter the credentials interactively.
After that should it also work non-interactive.
HTH
Jan
Am Donnerstag, 17. Mai 2012 10:36:43 UTC+2 schrieb Lee Winder:
>
> Hi Indyn
>
> I solved
Hi Indyn
I solved my problem by moving the executable calls outside of the build
process. I now have a few scripts constantly running in the background,
which the build process sends a message to when they want the executables
to run, and then waits for the executable scripts to flag back to t
Hello Lee and Jan,
I am having a similar problem. My batch script was simply:
-
cd "C:\Installs\Win32Forth 6.14.00"
start-both-RTests.exe
-
When I ran the job, the Console Output was:
Started by user anonymous
Building on master in workspace C:\Program Files (x86)\Jenkins\jobs
\Cl
Hi Lee,
afaik is the logged in user who triggers the job providing the
context. It does not matter who is logged on in case the job is
triggered via the cron job of Jenkins. The service account is then
used at all times.
You could amend the jenkins service credentials to a expicit user but
I would
Hi Jan
I'm unsure if the first step succeeds, as if I just run a batch script with
the same entry it fails for the same reason.
But you've given me a number of things to try here, so I'll give them a try
and see what the results are.
Just a quick question, I assume when running the job that Je
By the way.
It looks like some of your steps finish successfully right?
C:\Project\Asset_2\Export>C:\Project\Repository\Builder.exe --
a_lot_of_options_for_assets_2 is just failing if I dont get it wrong
Maybe you should prepend at each call
C:\Project\Asset_1\Export>C:\Project\Repository\Builder
What irritates me a bit is the exit code 255.
Thats a not quite usual one from a plain build step. Looks to me like
a return value from your builder.
The builder runs for sure? also when you build it in the workspace C:
\Program Files (x86)\Jenkins\jobs\02 - Daily
Build\workspace ?
I would always
Hi Jan, sorry, should have added this stuff but I was hoping the user
permission issue might have been a known problem :)
OS is Win7, Jenkins is running as a standalone service (default service as
set up by the Jenkins .msi installer -
http://jenkins-ci.org/content/windows-installers-are-
Hi Lee,
some more information would be nice. I did forget my crystal orb at
home ;)
Which OS are you using?
Do you run Jenkins as service?
A snippet of your batch files would be helpful as much as an outtake
of your build log would be.
Take care
Jan
On 19 Apr., 13:43, Lee Winder wrote:
> I have
I have a single batch file which calls a number of executables which builds
various assets for our application. When I run the batch file manually it
works perfectly (the command prompt opens, the assets are built - takes
about 10 minutes - and then it closes).
If I run this batch file via a b
13 matches
Mail list logo
