-
Improvement
-
Resolution: Fixed
-
Major
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.
- is blocking
-
JENKINS-16956 Require authentication for build triggers
-
- Resolved
-
- is related to
-
JENKINS-19922 "Build after other projects are built" job trigger causes permission check errors in case of enabled security
-
- Resolved
-
-
JENKINS-23686 Trigger "Build after other projects" does not work
-
- Resolved
-
-
JENKINS-25758 NPE when triggering downstream job (again)
-
- Resolved
-
[JENKINS-22397] A Trigger should be able to be a DependencyDeclarer
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is related to |
See https://github.com/jenkinsci/jenkins/pull/1168 and https://github.com/jenkinsci/buildresult-trigger-plugin/pull/9 for its usage.