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

blueocean header should show who replayed a job run

    Details

    • Similar Issues:

      Description

      I can look at a job header (e.g. /blue/organizations/.../detail/master/102/pipeline) and see this:

      If I click: 

      I'm taken to /job/.../master/102

      Which shows "Started by user" (core/src/main/resources/hudson/model/Cause/UserCause/description.properties: started_by_user)

      Note: I don't really need this for "push event to branch" as that is the reason.

      This appears to be:

      https://github.com/jenkinsci/workflow-cps-plugin/blob/9b768a42f60cc3389031646c24927fa062d444e1/src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/Messages.properties#L4

        Attachments

          Issue Links

            Activity

            jsoref Josh Soref created issue -
            jsoref Josh Soref made changes -
            Field Original Value New Value
            Assignee Josh Soref [ jsoref ]
            jsoref Josh Soref made changes -
            Remote Link This issue links to "PR#323 (Web Link)" [ 23618 ]
            Hide
            jsoref Josh Soref added a comment -

            I can see a couple of ways to do this:

            1. as in PR#323, changing the ReplayCause to report the user directly – there's a slight risk of showing the same information more than once.
            2. changing all clients of ReplayCause to do the same work – lots of consumers are stuck reinventing some code.
            3. changing blueocean to report (and try to flatten) all of the causes into this field – I don't think this will be particularly pretty (which is probably why it wasn't done already).

            I don't really care which way it's implemented, I'd just like to see the information I need when I'm looking at blueocean.

             

            Show
            jsoref Josh Soref added a comment - I can see a couple of ways to do this: as in PR#323, changing the ReplayCause  to report the user directly – there's a slight risk of showing the same information more than once. changing all clients of ReplayCause to do the same work – lots of consumers are stuck reinventing some code. changing blueocean to report (and try to flatten) all of the causes into this field – I don't think this will be particularly pretty (which is probably why it wasn't done already). I don't really care which way it's implemented, I'd just like to see the information I need when I'm looking at blueocean.  

              People

              • Assignee:
                jsoref Josh Soref
                Reporter:
                jsoref Josh Soref
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: