Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: buckminster-plugin
-
Labels:None
-
Similar Issues:
Description
I have a lot of builds that use a version number generated by the version number plugin. The property is not available in BM 1.0.5 but it works in version 1.0.3:
Example: Use "create a formatted version number", environment variable "civersion"
Add a shell task:
echo $civersion
--> This works well
Add a BM 1.0.5 task:
setpref targetPlatformPath=${civersion}
--> BM complains about the syntax, a value after the equals sign is required.
Attachments
Activity
I'm not using script files.
kullmanp
added a comment - I'm not using script files. There was a small issue in the custom map implementation I'm using for the property expansion. The fix is a 2-liner, unfortunately with the current infrastructure changes for java.net and hudson I have issues with my commit access and I'm unsure if the plugin release process is currently working.
There is an easy workaround until I can commit and release again: Simply name your env-var in upper case letters, i.e. CIVERSION instead of civersion.
If you do not want to use such a workaround you can easily patch the plugin yourself for now. Simply change the constructor in CaseInsensitiveMap like this:
public CaseInsensitiveMap(Map<? extends String, ? extends String> m) {
//super(m) would bypass the overridden put method and we would end up with lower case keys
super(m.size());
putAll(m);
}
jutzig
added a comment - There was a small issue in the custom map implementation I'm using for the property expansion. The fix is a 2-liner, unfortunately with the current infrastructure changes for java.net and hudson I have issues with my commit access and I'm unsure if the plugin release process is currently working.
There is an easy workaround until I can commit and release again: Simply name your env-var in upper case letters, i.e. CIVERSION instead of civersion.
If you do not want to use such a workaround you can easily patch the plugin yourself for now. Simply change the constructor in CaseInsensitiveMap like this:
public CaseInsensitiveMap(Map<? extends String, ? extends String> m) {
//super(m) would bypass the overridden put method and we would end up with lower case keys
super(m.size());
putAll(m);
} Thanks for the explanation. I can happily keep on working with 1.0.3 as long as it takes for the fix to come through.
kullmanp
added a comment - Thanks for the explanation. I can happily keep on working with 1.0.3 as long as it takes for the fix to come through. 
Are you happen to use this variable from within a script file? There's a known issue with variable replacement in script files:
http://issues.jenkins-ci.org/browse/JENKINS-7978
If not, I'll try to reproduce this with the version number plugin and post back once I know more.