After passing parameters 3 levels downstream (CI Build)> (SonarQube Quality Gate)> (Deploy to Dev)-> (Deploy to QA) all is correct. When passing to next downstream job (Deploy to UAT) the parameters are normally not passed. Is there a limit on the number (levels) of downstream jobs parameters can be passed?
Originally reported by sreilly91656, imported from: Parameterized Trigger Plugin -- not passing Predefined Parameters downstream
- status: Open
- priority: Major
- component(s): parameterized-trigger-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 2025-12-07
Raw content of original issue
After passing parameters 3 levels downstream (CI Build)> (SonarQube Quality Gate)> (Deploy to Dev)-> (Deploy to QA) all is correct. When passing to next downstream job (Deploy to UAT) the parameters are normally not passed. Is there a limit on the number (levels) of downstream jobs parameters can be passed?
After passing parameters 3 levels downstream (CI Build)
> (SonarQube Quality Gate)> (Deploy to Dev)-> (Deploy to QA) all is correct. When passing to next downstream job (Deploy to UAT) the parameters are normally not passed. Is there a limit on the number (levels) of downstream jobs parameters can be passed?Originally reported by sreilly91656, imported from: Parameterized Trigger Plugin -- not passing Predefined Parameters downstream
Raw content of original issue
All