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

a record needed why a build has started (what triggered it)

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • 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.

        1. patch.291
          15 kB
        2. patch.291.feb5
          19 kB
        3. patch.291.feb8
          20 kB
        4. patch.issue291.4feb
          17 kB

          [JENKINS-291] a record needed why a build has started (what triggered it)

          mdonohue added a comment -

          Created an attachment (id=546)
          Final patch - this is now committed as revision 15150

          mdonohue added a comment - Created an attachment (id=546) Final patch - this is now committed as revision 15150

          mdonohue added a comment -

          Now that we're committed, I'm marking this fixed.

          mdonohue added a comment - Now that we're committed, I'm marking this fixed.

          Alan Harder added a comment -

          this should be mentioned in changelog.html, and check the unit tests for new
          breakages..

          Alan Harder added a comment - this should be mentioned in changelog.html, and check the unit tests for new breakages..

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/main/core/src/main/java/hudson/model/Cause.java
          trunk/hudson/main/core/src/main/java/hudson/model/CauseAction.java
          trunk/hudson/main/core/src/main/java/hudson/triggers/SCMTrigger.java
          trunk/hudson/main/core/src/main/java/hudson/triggers/TimerTrigger.java
          http://fisheye4.cenqua.com/changelog/hudson/?cs=15237
          Log:
          JENKINS-291 Export CauseAction so exported Causes can be accessed via /api/.
          Export base Cause class and its short description instead of on every subclass.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/main/core/src/main/java/hudson/model/Cause.java trunk/hudson/main/core/src/main/java/hudson/model/CauseAction.java trunk/hudson/main/core/src/main/java/hudson/triggers/SCMTrigger.java trunk/hudson/main/core/src/main/java/hudson/triggers/TimerTrigger.java http://fisheye4.cenqua.com/changelog/hudson/?cs=15237 Log: JENKINS-291 Export CauseAction so exported Causes can be accessed via /api/. Export base Cause class and its short description instead of on every subclass.

          ejono added a comment -

          This is awesome! Thank you very much for doing this. However, it would be much
          nicer if it displayed upstream builds as a link to that particular build rather
          than just a textual description.

          ejono added a comment - This is awesome! Thank you very much for doing this. However, it would be much nicer if it displayed upstream builds as a link to that particular build rather than just a textual description.

          mdonohue added a comment -

          > it would be much nicer if it displayed upstream builds as a link
          > to that particular build rather than just a textual description.

          This would best be handled by a new enhancement request, or becoming a
          contributor yourself.

          mdonohue added a comment - > it would be much nicer if it displayed upstream builds as a link > to that particular build rather than just a textual description. This would best be handled by a new enhancement request, or becoming a contributor yourself.

          ejono added a comment -

          Yeah, I guess so. Maybe once I graduate I'll become a contributor.

          ejono added a comment - Yeah, I guess so. Maybe once I graduate I'll become a contributor.

          Alan Harder added a comment -

          that request is issue #3054

          Alan Harder added a comment - that request is issue #3054

          mdonohue added a comment -
              • Issue 2123 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 2123 has been marked as a duplicate of this issue. ***

          mdonohue added a comment -
              • Issue 2522 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 2522 has been marked as a duplicate of this issue. ***

            mdonohue mdonohue
            gradopado gradopado
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: