[JIRA] (JENKINS-15024) Inline authentication prevents incremental updates

[jgl...@cloudbees.com (JIRA)]

Jesse Glick resolved JENKINS-15024 as Not A Defect Inline authentication prevents incremental updates Unfortunately if you clone https://username:passw...@repository.com your .hg/hgrc in the workspace will be just [paths] default = https://usern...@repository.com meaning that a subsequent hg pull from the plugin will prompt for a password (and fail since it is run noninteractively). So while it may be annoying to have your workspace checked out anew, this is better than not being able to update at all. Of course nicest would be to somehow integrate with the Credentials plugin so that you could store your password securely on Jenkins master, transmitting it to the slave just long enough to be passed somehow to pull and other commands, perhaps using a masked --config auth.something.password=… parameter. But this is a matter for a separate, and broader, RFE. In the meantime the best bet is to preconfigure authentication on those nodes which will be running Mercurial commands. Change By: Jesse Glick (19/Sep/12 3:27 AM) Status: In Progress Resolved Resolution: Not A Defect

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira