Don't process build results prematurely

I'd love to have a unit test for this, but didn't manage to write one yet.
added some stars
Merge pull request #34 from raboof/fix_premature_promotion

Don't process build results prematurely
Merge pull request #35 from BMarvi/master

added some stars
Does not need to assume that the ancestor is a Job, we can live with an Item
corrected  capital letters  in silver stars
Added PROMOTED_USER_NAME environment variable
Unit test for Promoted_user_name variable
Fixing spacing issue in Promotion.java
Fix unit test for promoted_user_name
Merge pull request #36 from BMarvi/master

corrected  capital letters  in silver stars
Fix spacing issue.
- [FIXED JENKINS-22005]
- Adding ManualCondition Test Cases and making a few changes for supporting them.
Merge pull request #37 from cchong/master

[FIXED JENKINS-16063] Added PROMOTED_USER_NAME environment variable
[maven-release-plugin] prepare release promoted-builds-2.16
[maven-release-plugin] prepare for next development iteration
Merge pull request #39 from cvarjao/JENKINS-22005

FIXED JENKINS-22005
[maven-release-plugin] prepare release promoted-builds-2.17
[maven-release-plugin] prepare for next development iteration
Export build display name to promotion job

Build display name is often more useful than the build id, as
users of things like the Version Number Plugin will generate
meaningful build numbers and set them as the build display
name. Such build numbers will then be the thing that you
actually need during a promotion if your artifact was stored
somewhere other than Jenkins.