[
https://issues.jenkins-ci.org/browse/JENKINS-12528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159252#comment-159252
]
Gavriil Konovalenko commented on JENKINS-12528:
-----------------------------------------------
Presence of following string in the build log output: "Legacy code started
this job. No cause information is available" means that username is not
identifiable. Because source for username data is Cause, which is absent.
I'd suggest to reassign this bug to
https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin , asking to
fix absence of build Cause.
> Started-By Environment Variable Plugin does not work in manually approved
> promoted builds
> -----------------------------------------------------------------------------------------
>
> Key: JENKINS-12528
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12528
> Project: Jenkins
> Issue Type: Bug
> Components: promoted-builds, started-by-envvar
> Reporter: Hua Zhang
> Attachments: promoted-build-started-by-not-working.png,
> promoted-build-started-by-working.png
>
>
> Start-By Enviorment Varialbe plugin works olny with "Force Promotion" of
> Promoted Builds plugin.
> In a promotion process, if option "Only when manually approved" (under
> section "Criteria") is selected, and the user promotes the build (on
> "Promotion Status" page) by clicking "Approve" button, JENKINS_STARTED_BY
> will not be correctly populated. In console output:
> {code}
> Legacy code started this job. No cause information is available
> ...
> + echo JENKINS_STARTED_BY=
> JENKINS_STARTED_BY=
> {code}
> If this option is not selected, therefore the user can only promote a build
> by clicking "Force Promotion" (if he has the privilege), then
> JENKINS_STARTED_BY variable is populated correctly. In console output:
> {code}
> Started by user john
> ...
> + echo JENKINS_STARTED_BY=john
> JENKINS_STARTED_BY=john
> {code}
> In attachment are screen-shots of a trivial Jenkins job configuration
> demonstrating the test cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
