-
Bug
-
Resolution: Fixed
-
Major
-
None
Scenario
ProjectA triggers ProjectB
ProjectB has a RunParameter for ProjectA with a filter set for Successful Builds Only. The Run Parameter uses the PeepholePermalink to determine the LastSuccessful build.
When ProjectA completes successfully, it will trigger a build of ProjectB before the PeepholePermalink cache is updated. This causes the RunParameter to default to the previous successful build of ProjectA, not the one which has just completed.
- is duplicated by
-
JENKINS-27635 Downstream build can start running before upstream build has completed
-
- Resolved
-
- is related to
-
JENKINS-16023 Lazy loading causes massive delays after a period of inactivity when loading dashboard
-
- Resolved
-
-
JENKINS-980 Race condition between build trigger and build completion
-
- Closed
-
-
JENKINS-22800 Downstream build does not wait for upstream build to complete
-
- Open
-
-
JENKINS-20857 Default Run Parameter on First Triggered Job Causes NullPointerException
-
- Resolved
-
[JENKINS-20989] PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link | New: This issue is related to JENKINS-22800 [ JENKINS-22800 ] |
Link |
New:
This issue is duplicated by |
Assignee | New: Oliver Gondža [ olivergondza ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 152830 ] | New: JNJira + In-Review [ 194364 ] |