Dear all, Consider a multiconfiguratin project with two axes: one for slaves and one for a feature that can be either enabled or disabled.
For the moment, I have encoded the feature axis with a label named "feature" which can take the two values "true" and "false". In Jenkins' user interface, this axis is shown by just printing the values, "true" and "false", which is unclear to the user. And also, this does not scale: if I add another axis for another feature according to the same principle, things will really become ambiguous. My question is: is there a way to tell Jenkins to also display labels rather than just their values? For instance, rather than false and true, is it possible to get something like feature=false and feature=true? I realise that there is the possibility to have more descriptive values than false and true. For instance, the values for the feature label could be something like "with_feature" and "without_feature", which would make the current Jenkins display clear and non-ambiguous. It's just that I like the booleans which make the shell script light, since you can do things like if $feature; then ... fi So if there is no way to change Jenkins' display I will adapt the values and make them more descriptive and handle this in the build scripts, but before resorting to this solution I wanted to ask here. Any suggestion is welcome! Thanks, Sébastien. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170511141855.wiefnfyjyryae64j%40pl-59055.rocqadm.inria.fr. For more options, visit https://groups.google.com/d/optout.
