"Execute Windows batch command" not executing

[jon...@gmail.com]

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
Building in workspace C:\jenkins\sdk
Triggering default
default completed with result SUCCESS
Finished: SUCCESS

Thank you for any suggestions.

Jon

[jon...@gmail.com]

Also I wonder what "default" is, and what exactly it triggered.. Output seems really limited. Is there a verbose output option?

[Gavin Goodrich]

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?

[Daniel Beck]

On 26.06.2014, at 00:35, Gavin Goodrich <gaving...@gmail.com> wrote:

> default

That's the default matrix/multi-project configuration name for the single existing sub-project if there are no axes defined.

Compare the following two URLs to see the difference:

Meta-job just triggering configuration builds: /job/(jobname)/(buildnumber)/console
'default' configuration build with actual output: /job/(jobname)/default/(buildnumber)/console

[Notes Jonny]

Hi Daniel

Thank you for your reply.

I found the issue, added it to ticket here:

https://issues.jenkins-ci.org/browse/JENKINS-23540

Essentially the "Build multi-configuration project" seems very
unreliable. As soon as I changed to "Build a free-style software
project" my builds started working.

Its a shame that multi-configuration is not stable.. also I saw that
it does a dup checkout of whole repository, with another copy in a
"default" subfolder.

Perhaps I am not understanding multi-build though.. I only need to run
on a single computer.

Regards, Jon

> --
> You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/CNM84SYPNqQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Notes Jonny]

Hi

Thank you for your reply.

Someone else found same issue, seems multi-build is not reliable, so I
changed to standalone builds.

http://stackoverflow.com/questions/13756215/jenkins-console-output-is-virtually-empty