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

A Trigger should be able to be a DependencyDeclarer

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          is blocking

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-16956 Require authentication for build triggers

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-19922 "Build after other projects are built" job trigger causes permission check errors in case of enabled security

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-23686 Trigger "Build after other projects" does not work

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-25758 NPE when triggering downstream job (again)

          • Major - Major loss of function.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: