I really don't like how I have to provide the Maven "settings.xml" file to my build job. I know I can override the default GUID value, but the whole mechanism just seems odd.
What I would LIKE to see is exactly how a "Credential Parameter" works. In the job configuration, I just specify the principal I want, and my script receives it as an opaque value that doesn't need to be hardcoded anywhere. I'd like to be able to provide a "File ID parameter" the same way, just selecting the managed file from a dropdown, so nothing needs to care about what the actual value is. Scripts should never have to have GUID values hardcoded, or values substituted for GUID values. I know there is a "File Parameter", but that seems to be something different. I'm not even sure what that does. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5a10b901-ceb8-4a22-9e72-bd29c1abf99a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
