Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45412

Determine how a job was started

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Any Jenkins job should be able to determine how it was started. Among the possible methods is (1) directly started by a user, (2), started by another job (chaining jobs), and (3) started by a job management plugin like the multijob plugin.

      Presently, the only way I've found to determine this information is to parse the log file and inspect the line starting "started by". This does not seem to be a proper method (though it works, thus far, for me). Finding the correct log file is a tricky process.

      By a proper method, I mean one which is documented and which a user can rely on to continue through future updates. It should not require filesystem actions (like "ls -r").

        Attachments

          Activity

          daveclose Dave Close created issue -
          Hide
          yorammi Yoram Michaeli added a comment -

          Closing issue as part of tikal-multijob-plugin issues cleanup.
          If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)

          Show
          yorammi Yoram Michaeli added a comment - Closing issue as part of tikal-multijob-plugin issues cleanup. If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)
          yorammi Yoram Michaeli made changes -
          Field Original Value New Value
          Resolution Postponed [ 6 ]
          Status Open [ 1 ] Closed [ 6 ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            daveclose Dave Close
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: