Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
This is regression properly due to JENKINS-51680 where my downstream job depends on a maven module/artifact of the upstream snapshot
Revert back 3.5.9 to get auto trigger working again
Attachments
Issue Links
- is related to
-
JENKINS-51680 Infinity Build Loop
-
- Closed
-
-
JENKINS-51953 Better pipeline Upstream Cause with details of the Maven artifact that caused the trigger
-
- Closed
-
-
JENKINS-53392 Support multiple artifact as cause on MavenDependencyUpstreamCause
-
- Closed
-
-
JENKINS-53396 Verify downstream pipeline eligibility only once when multiple generated maven artifacts trigger a pipeline
-
- Closed
-
I deployed the latest from source. Upstream jobs did not come to complete after 40 minutes ( ie any ending logger about triggering). I ended up to revert back to 3.5.9
The interesting is the double downstream trigger issue was there all along.
Thought of reverting changes at 3.5.10 where problem started?