Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Component/s: core
-
Labels:None
-
Environment:Windows XP, Red Hat Enterprise Linux 5
-
Similar Issues:
Description
The global properties system is not working as (I) expected. Tried using the Hudson release plugin, Tasks plugin, Ant build, can't pass any property.
Steps:
1. Enter Manage Hudson -> Configure system -> Global properties.
2. Define a new global property: ABC, value 123.
3. Try to access it from a task, from the release plugin, from an Ant build (via command line), using the documented syntax:
$ABC or ${ABC}.
4. Result - no replacement.
This is pretty serious for us since we have lots of jobs. For example several plugins use system tools: Maven 2, SVN, ... We've already configured the paths to these tools, several versions even, in the global Hudson configuration.
However, because of this bug, we have to replicate them for every job. Error prone and added complexity.
Attachments
Issue Links
- is related to
-
-
- Reopened
-
Activity
This also happens on 1.509.3 LTS. Did not happen with Hudson (www.hudson-ci.org) though, so this is Jenkins specific.
Sebastian M.
added a comment - - edited This also happens on 1.509.3 LTS. Did not happen with Hudson (www.hudson-ci.org) though, so this is Jenkins specific. Assigned the issue to a proper component.
This needs to be reproduced on a recent Jenkins version with clear instructions how to reproduce.
Note that global properties are provided mostly as environment variables to build steps, so run set (Windows, Batch build step) or env (Linux, Shell build step) to see whether it's actually not defined, or just not passed to e.g. Ant as system property.
Also, need to reproduce with EnvInject plugin disabled if you're filing a core bug.
I don't remember when this started working but under 1.532.2 and EnvInject 1.89, this is no longer a problem. In the release notes for EnvInject 1.88 this problem has been corrected.
Walter Kacynski
added a comment - I don't remember when this started working but under 1.532.2 and EnvInject 1.89, this is no longer a problem. In the release notes for EnvInject 1.88 this problem has been corrected.
I just noticed this problem and I don't remember it being this way on previous releases of jenkins. This only happens on my slaves running 1.510 and remoting 2.23