jenkinsci / jenkinsci/parameterized-trigger-plugin

[JENKINS-22564] Env variables not passed to job

Open
#595 0 comments 0 reactions 0 assignees View on GitHub
component:parameterized-trigger-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
77
Forks
174
Avg merge
22h 27m
Merged PRs (30d)
1

Description

I think there is a bug. Or documentation is not correct. Regarding env variables.

When using the "Trigger/Call builds on another project" item.

If the trigger is configured with the "Block until the triggered projects finish their builds" enabled, the following Environment variables are made available for further build steps


https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin

Above statement is not true in 2.22. I have this setup but also no environment variables.

---
Originally reported by onknows, imported from: Env variables not passed to job


  • status: Open
  • priority: Major
  • component(s): parameterized-trigger-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-12-07

Raw content of original issue

I think there is a bug. Or documentation is not correct. Regarding env variables.

When using the "Trigger/Call builds on another project" item.
If the trigger is configured with the "Block until the triggered projects finish their builds" enabled, the following Environment variables are made available for further build steps


https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin

Above statement is not true in 2.22. I have this setup but also no environment variables.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.