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

A Trigger should be able to be a DependencyDeclarer

      It is common for a Publisher to be a DependencyDeclarer: an upstream project which kicks off a downstream project can thus add an edge to the dependency graph. But the converse should also be true: if a downstream project has a (non-pseudo) Trigger which involves an upstream project, it should be able to record that as an edge, too.

          [JENKINS-22397] A Trigger should be able to be a DependencyDeclarer

          Jesse Glick created issue -
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-19922 [ JENKINS-19922 ]
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-16956 [ JENKINS-16956 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-23686 [ JENKINS-23686 ]
          Steffen Sledz made changes -
          Link New: This issue is related to JENKINS-25758 [ JENKINS-25758 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 154498 ] New: JNJira + In-Review [ 194924 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: