Triggering default sounds like you are triggering another job to run as part of this jobs execution. Are you doing this explicitly? I'm pretty sure that .bat files are not the only thing supported by the run windows batch command build step. My server doesn't call any...just straight windows commands.
So do you have the command split into different build steps or is this two lines in one build step? On Wednesday, June 25, 2014 9:16:36 AM UTC-5, [email protected] wrote: > > Hello > > I created a multi-configuration project. I find that my commands are not > executing always. Sometimes they do work sometimes they don't. I cannot > understand why. Any ideas? > > I wonder if only "BAT" files are supported? although even if I just have > 2nd command, still does not work 100% of the time. > These setting worked perfectly on previous Hudson machine I use. > > I have two commands: > > 1st: > @echo build folder: %cd% > > > 2nd: > internal_build.bat > > > Output: > > Started by user anonymous <http://bed7417.ad.ree.renesas.com:8080/user/null> > Building in workspace C:\jenkins\sdk > Triggering default > <http://bed7417.ad.ree.renesas.com:8080/job/sdk_dev_cfg01/default/>default > <http://bed7417.ad.ree.renesas.com:8080/job/sdk_dev_cfg01/default/> completed > with result SUCCESS > Finished: SUCCESS > > > Thank you for any suggestions. > Jon > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
