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
another
> > action may lead to an anonymous user latest for the action/second file
> > call (if embedded).
> > So calling a btach file that calls the builder.exe would not be my
> > first choice ;)
> >
> > Take care
> > Jan
> >
> > O
t;
C:\Project\Repository\Builder.exe --a_lot_of_options_for_assets_2
Console output is simply the content of the batch file followed by failure
Started by user Lee Winder
Building in workspace C:\Program Files (x86)\Jenkins\jobs\02 - Daily
Build\workspace
[workspace] $ cm
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
