

JENKINS-43507 Allow SCMSource and SCMNavigator subtypes to share common traits.JENKINS-45806 Branch scanning failed to pass credentials. JENKINS-42278 Branch scanning failed if some branches lacked the marker file such as Jenkinsfile. Metadata fixes useful for downstream plugins.Mulibranch pipeline job and mercurialSCMSource traits request Closed Using the repository cache without sharing failed on Windows.Mercurial plugin cannot handle spaces in file names Resolved
TORTOISEHG PUSH COMMAND RETURNED CODE 1 INSTALL
For example, in /configure under Mercurial installations, add a Mercurial installation with whatever Name you like, Executable = INSTALLATION/bin/hg, Install automatically, Run Command, Label = linux (if desired to limit this to slaves configured with the same label), Command = || wget -q -O - | xzcat | tar xvf - (or …/x86_64/… for 64-bit slaves), Tool Home = usr, and configure a job with this installation tied to a Linux slave. For users of Linux machines (with Python preinstalled), you can use ArchLinux packages. The plugin supports generic tool auto-installation methods for your Mercurial installation, though it does not publish a catalog of Mercurial versions. since this number may be different in each clone of a repository, it is generally better to use MERCURIAL_REVISION. MERCURIAL_REVISION_NUMBER: the revision number for the changeset being built.


Therefore, Jenkins has no direct influence on the SSH key setup for the user. Jenkins -> Mercurial Plugin -> TortoiseHG > plink/pageant TortoiseHG integrates directly with pageant/putty for it's ssh connections, and the toolkit in jenkins only calls the executable, so it looks like:
