Hi Jonathan.
A) Try opening the configuration of your "sdk_dev_cfg00" and the "build" projects - and save again (Because I see "Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered")

B) Wrt to your build step, it Is type Windows Batch file - am I right ?
C) Try change in change the commands:
Build Step1, type windows batch: echo %WORKSPACE%
Build Step2, type windows batch: dir

Be aware that for some post-build step plugins, they can be ordered, and sometimes (depends on the plugin), subsequent steps are aborted if one fails
The above two is just to verify both build steps are executed and not failing.

Hi Jens

Thank you for your reply.

I had a breakthrough, found this website where someone else had the same problem:
http://stackoverflow.com/questions/13756215/jenkins-console-output-is-virtually-empty

So when I used "Build multi-configuration project" it did not work reliably

Since I changed to "Build a free-style software project" my builds work reliably. e.g. builds run once (rather than duplicate), output is present (rather than missing).

It is straight forward to reproduce on Windows7. Could I ask you to try:

1) Install latest Jenkins
2) Create multi-configuration project
3) add a build step like mine "@echo test"
4) add svn checkout.
5) Run

Hi Jonathan.
Thats right - matrix builds can be a bit of a pain, I avoid the as much as I can. Anyway, I will change the component and assignee for this, as it is not related to the component "component"
Br
Jens

Many thanks Jens
My "Build a free-style software project" are working well. So I will stay using these now.

Removing pseudolink to Praqma's internal tracker.

@Jonathan
Do you still think it's a defect in matrix-project?
I think that the referenced stackoverflow question explains the behavior

Hi Oleg
Thank you for your message.
I couldn't understand it myself, but if you think it is ok, then the ticket could be closed.
perhaps an explanation could be added to jenkins warning most users not to use "multi configs" and stick to "Build a free-style software project"

> perhaps an explanation could be added to jenkins warning most users not to use "multi configs" and stick to "Build a free-style software project"

I don't agree with this statement.
It makes sense to extend documentation of Matrix Project Plugin, but the plugin works well. Users just need to know about it's common behavior

Hi Oleg

Perhaps just saying [Most new users may find it clear to have multiple "Build a free-style software project"]

For me, I have 20 build configurations.. I made the mistake of thinking I needed "multi configs".

As a new-starter, who has never used Jenkins, my perspective is that we make assumptions and understanding based on what we read. Currently it was confusing for me as a new-starter, it wasn't what I expected.

Could simpler names be also used? "Build a free-style software project" is a bit of a mouthful
i.e

"Complex multi-config"
"Solo config"

/newJob on 1.532.3 says:

Build a free-style software project
This is the central feature of Jenkins. Jenkins will build your project, combining any SCM with any build system, and this can be even used for something other than software build.

Build multi-configuration project
Suitable for projects that need a large number of different configurations, such as testing on multiple environments, platform-specific builds, etc.

TBH, looks pretty straightforward to me. Anything more and it'll discourage users from using multi-config for legitimate use cases.

Of course, suggestions for different wording are welcome, e.g. to point out that multi-config generally builds your project multiple times in parallel. (Best done as pull request on GitHub – just grep the sources for parts of these lines to find where it's defined.)

Could simpler names be also used? "Build a free-style software project" is a bit of a mouthful

Newest Jenkins releases call it just "Freestyle Project". Multi-config is changed as well: https://github.com/jenkinsci/matrix-project-plugin/commit/611d4b1d167fdf2bf92b9a2f1ae4fa54dc08d9a0