Merge branch 'master', remote-tracking branch 'remotes/parent/master'
First Version showing Subprojects without using the dependency Graph
added a new parameter type that lets you restrict the subset of the matrix to run
[maven-release-plugin] prepare release parameterized-trigger-2.14
[maven-release-plugin] prepare for next development iteration
[FIXED JENKINS-8916] Allowing same type of parameter for triggered build
more than once seems redundant

It requires Jenkins core version 1.463 to work, but it's fully
backwards compatible.
Merge pull request #20 from fredg02/master

[FIXED JENKINS-8916] Allowing same type of parameter for triggered build more than once seems redundant
fix minor error message formatting issue
projectList can't be cached : in case projectList is computed form env,
it will not be re-computed on env changes
[maven-release-plugin] prepare release parameterized-trigger-2.15
[maven-release-plugin] prepare for next development iteration
Merge branch 'master' of https://github.com/jenkinsci/parameterized-trigger-plugin
Test cases to show [JENKINS-14278] occuring.
Get the root build before getting the project so that we get the correct parent.

This means that when the build is one of a matrix configuration group we get the matrix parent,
and therefore when getting the project list we do so from the Item group that the parent is in,
not the child's (the matrix configurations).
Merge fixes from kinow to actually set the number of executors.
Add behaviour options for counter factory in case of invalid options.

[FIXED JENKINS-13872]
Add the possibility of skipping the triggering, or ignoring the parameters when the
to, from and step elements do not form a contained set.

Corrected an issue in the BuildTriggerConfig class where if a factory returned no parameters
meant that no projects would be triggered in certain cases.
clarify error when no parameter set and 'triggerWithNoParameter' unchecked
Make the FilebuildParameter factory behave in similar way to counter factor

Add behaviour to handle cases where there are no files found in the workspace matching
expression.
This allows the following cases: failing the build, triggering without these parameters
and skip triggering of the projects if the files don't exist.
capture build environment from BuildTrigger so that parameters can get expanded.
[FIXED JENKINS-15130] ‘descriptorByName/BuildTrigger’ ambiguous.