Hi,
Can you re check the logic (change the result of the Run condition that is inside the not) and try again?

The line "Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]"
is actually stating that the Run condition called "Not" is preventing the step called "Trigger param..." from being run.

So from that output, I would not have expected the parameterized trigger step to have executed.

I tested the always and not string == string cases

Always case:

Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]

not string == string case:

Strings match run condition: string 1=[], string 2=[]
Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]

both gave the same results,

The reason is that the trigger parameterized build performs no action in the Perform code.
This is because it creates Dependancy's that it attaches to the DependancyGraph in
buildDependencyGraph() which is part of the DependecyDeclarer interface

	@Override
	public void buildDependencyGraph(AbstractProject owner, DependencyGraph graph) {
		// Can only add dependencies in Hudson 1.341 or higher
		if (!canDeclare(owner)) return;

		for (BuildTriggerConfig config : configs)
			for (AbstractProject project : config.getProjectList(null))
				ParameterizedDependency.add(owner, project, config, graph);
	}

Sorry, I just saw the the 2nd entry - my bad.

I'll try to have a look at this this evening and see if there is anything that can be done from the Flexible publish side (other than just adding the parameterized trigger to the list of excluded steps)

Code changed in jenkins
User: bap2000
Path:
src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java
src/main/java/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisher.java
http://jenkins-ci.org/commit/flexible-publish-plugin/ca9d155ed5930eecacea781b63d99afcaf18da26
Log:
Allow contained steps to participate in building the dependency graph

[FIXED JENKINS-12418]

Can you build HEAD of master and try out the changes?

Don't bother!
Unfortunately, when using the change above, the conditions are ignored and the downstream builds will always be triggered.

I will add the parameterized trigger to the list of excluded publishers.

Ok, I expected this,
I will work on the parameterized trigger to add run condition support replacing existing job result only.

cjo9900, do you fix this issue ? If yes, when do you plan to re-add the parameterized trigger into the Flexible plugin list of available publishers ?

The fix was to add the functionality to the parameterized trigger, as there is no way that the flexible publish can affect the Dependancies that are created.

See Pull request for it.
https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17

@cjo9900, from the comments I thought that fixing issue is waiting for merge of pull request 17 in parameterized-trigger-plugin, but when I asked there the reply was that it rather seems to be already fixed here. How does it really look like?