Hi Stephan, unfortunately I was not able to catch you lately on the chat, but I have question I want your opinion before I go ahead with my implementation.
I'm working on the credentials integration for the settigns.xml again and I have some questions about the usage of domains in the credential plugin… I understand that its a good way to group the credentials on the credentials UI, but it does not help when selecting the correct credentials at any other location from within a dropdown. In my case DomainRequirements are not usable to select/limit the correct credentials. This because I have no idea how the user will have the server configured - thats done in the pom.xml and not in the settings.xml (he could use scp, http, ssh… to deploy or copy artifacts around). From a maven point of view it does not matter how the connection to the server is configured, the credentials are always stored the same way in the settings.xml. >From my point of view - an admin would like to group his credentials like >this: e.g. "My slave connection credentials", "my maven settings >credentials",…. and then in the screen for the settings.xml he want to see all >the ones from the group for the maven settings. So my DomainRequirement would >more be like: get me all credentials from the "settings.xml domain A" instead >of "all for http to host X with port Y". Whats your view on this? regards Domi -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
