-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Platform: PC, OS: Linux
It would be good to know what a build triggered. When a user triggered it via
the web-site I would like to know who it was (that requires authentication).
Other build reasons: a succeeded build of another project, a wget request by a
script, a cron trigger.
- is blocking
-
JENKINS-2898 Ability to change ant target depending on build trigger
- Open
-
JENKINS-324 Allow a description to be set when triggering remote build
- Closed
-
JENKINS-1628 Add logged-in username to batch-task environment vars
- Closed
-
JENKINS-2914 Audit Trail Plugin does not record schedule/poll-scm triggered builds
- Closed
-
JENKINS-3166 Token listing all triggers of a build
- Closed
- is duplicated by
-
JENKINS-1124 Information about what triggered the build
- Closed
-
JENKINS-2123 Ehancement: record trigger events
- Closed
-
JENKINS-2522 Display user name with each build
- Closed