You didn't update Hudson itself?

Really strange as it looks to me that when it doesn't work it shouldn't work with downstream-ext 1.2, either.

Looks for me like the dependency resolution for matrix projects in Hudson core is broken:
When looking for downstream projects it only checks for dependencies of the current MatrixConfiguration and not for the MatrixProject itself.

I could add a workaround, so it works for matrix projects again, but that would seem more like a hack to me. I think this should be addressed in Hudson core.

Or did you mean you downgraded to downstream-ext 1.1?
That would explain everything.

Code changed in hudson
User: : kutzi
Path:
trunk/hudson/plugins/downstream-ext/src/main/java/hudson/plugins/downstream_ext/DownstreamTrigger.java
http://jenkins-ci.org/commit/27090
Log:
JENKINS-5508 workaround for MatrixProjects not being triggered anymore

Strange, I am using 1.2 with Hudson 1.341. I do see that downstream Jobs were triggered by the parent Matrix Job after I switched back to 1.2 from 1.3, but the last time that happened was on Friday, and now the parent Jobs are no longer triggering the downstream Jobs, only the children. I can't explain it, but there it is.

Should be fixed 1.4 or better said: I added a workaround for what I think is a Hudson core issue - I started a thread on the developers list about it

I've upgraded to version 1.4 of the plugin (still using 1.341 of hudson itself) and it seems that only the individual Configurations (child Jobs), but not the main parent Job, trigger the downstream projects. I thought from your comment above that you had a fix for this – or did I misunderstand and this is the expected behavior now?

Can we discuss this offline (kutzi@dev.java.net)
I guess I have only a limited understanding about how matrix jobs actually work.