#GIT TORTOISEHG SSH GENERATOR#

Allow credentials pulldown to work in Snippet Generator from a Pipeline branch project.

Excessive numbers of changesets were being considered by polling under some circumstances.

JENKINS-30120 As of Mercurial 3.4.2, polling was broken when using spaces in a branch name.

JENKINS-36219 Changelogs were not displayed for multibranch (e.g., Pipeline) projects.

JENKINS-28121 Pipeline checkouts could fail if the workspace directory did not yet exist.

JENKINS-37274 Suppressed some output in the build log that seems to have misled users.

JENKINS-30295 Implemented APIs used by the Email-ext plugin.

Added an option to check out a revset rather than a branch.

JENKINS-23571 Configurable master cache directory location.

JENKINS-40836 Report the primary branch ( default) to multibranch UIs.

JENKINS-39355 Using new SCM APIs, in particular to better support webhook events in multibranch projects.

other changes Unknown User (stephenconnolly) forgot to list.

Please read this Blog Post before upgrading.

JENKINS-41814 Expose event origin to listeners using the new SCM API event system.

JENKINS-26762 Ignore trailing slashes when comparing URLs for /mercurial/notif圜ommit. JENKINS-41657 Better support Mercurial for Pipeline library configuration. JENKINS-26100 Support exporting environment variables to Pipeline scripts, when on Jenkins 2.60 and suitably new plugins.

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

#GIT TORTOISEHG SSH 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.MERCURIAL_REVISION_SHORT: the short version of changeset ID (SHA-1 hash) that uniquely identifies the changeset being built.MERCURIAL_REVISION: the changeset ID (SHA-1 hash) that uniquely identifies the changeset being built.The plugin exposes two new environment variables that can be used in build steps: This differs from the linux/cygwin environment where the ssh keys by convention are stored under ~/.ssh. 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:

Git tortoisehg ssh