An actual use case for this might be helpful. Right now, this looks a lot like an XY problem [1].
Also, a possible solution is a Choice parameter with only one value to select. But note that e.g. Parameterized Trigger will just override this when you specify a different value there, so it's on the UI only. 1: http://www.perlmonks.org/?node_id=542341 On 21.07.2013, at 22:53, Thomas Fields <thomasmfie...@gmail.com> wrote: > >>No, that I am aware of. I've been kind of thinking about something similar > but more of like a set of variables that can be defined with the job, and > then referenced in multiple places within the job configuration. > Yeah, something like this would be perfect for my needs. > > Surely it's not too difficult to add a new "read only string parameter" to > the parameter options in the job description then display it but obviously > don't let the user edit it. Did you enter this in Jira already? > > Cheers > Tom > > -- > 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. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
