Git Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID git Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
2.2.1
Apr 12, 2014
1.509
multiple-scms (version:0.2, optional)
token-macro (version:1.10, optional)
credentials (version:1.10)
parameterized-trigger (version:2.4, optional)
scm-api (version:0.2)
git-client (version:1.8.0)
promoted-builds (version:2.17, optional)
ssh-credentials (version:1.6.1)
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Kohsuke Kawaguchi (id: kohsuke)
Nicolas De Loof (id: ndeloof)
Usage Installations 2013-Apr 25907
2013-May 26964
2013-Jun 27687
2013-Jul 29423
2013-Aug 30202
2013-Sep 31116
2013-Oct 33588
2013-Nov 33483
2013-Dec 33354
2014-Jan 36196
2014-Feb 37646
2014-Mar 39746

This plugin allows use of Git as a build SCM. A recent Git runtime is required (1.7.9 minimum, 1.8.x recommended). Plugin is only tested on official git client. Use exotic installations at your own risks.

Configuration 

Repository URL should be in the format:

git@hostname.com:repository

Though arguably this is not a true URL, this is ssh compact format.  To test at the command line run: git.exe ls-remote <URL> 

Bugs

  • Check the open issues carefully to see if the issue has already been reported
  • Create an issue if needed, and make sure to choose the git sub-component.  Make sure to mention the plugin version number in the issue description.

Note: Source code can be found at https://github.com/jenkinsci/git-plugin.

Gotchas

  • If you are seeing output indicating Git could not clone, something like the output below, go to to the Jenkins configuration settings (not the project settings, the global ones) and change the Git path to a fully qualified path (eg. not "git" but "/usr/bin/git" or wherever your Git binary is installed). You should also verify that the permissions are correct if you are doing a file system based clone.
Started by user anonymous
Checkout:workspace / C:\Documents and Settings\Administrator\.hudson\jobs\watir\workspace - hudson.remoting.LocalChannel@1a1f370
Last Build : #4
Checkout:workspace / C:\Documents and Settings\Administrator\.hudson\jobs\watir\workspace - hudson.remoting.LocalChannel@1a1f370
Cloning the remote Git repository
Cloning repository origin
$ git clone -o origin git://github.com/bret/watir.git "C:\Documents and Settings\Administrator\.hudson\jobs\watir\workspace"
Trying next repository
ERROR: Could not clone from a repository
FATAL: Could not clone
hudson.plugins.git.GitException: Could not clone
    at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:400)
    at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:358)
    at hudson.FilePath.act(FilePath.java:676)
    at hudson.FilePath.act(FilePath.java:660)
    at hudson.plugins.git.GitSCM.checkout(GitSCM.java:358)
    at hudson.model.AbstractProject.checkout(AbstractProject.java:833)
    at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:314)
    at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:266)
    at hudson.model.Run.run(Run.java:948)
    at hudson.model.Build.run(Build.java:112)
    at hudson.model.ResourceController.execute(ResourceController.java:93)
    at hudson.model.Executor.run(Executor.java:118)
  • You may need to tell git who the user Jenkins is running as. To do this on a Linux/Unix system switch to that user which is probably tomcat6. Do this by using either of the following, which work even if the user is not supposed to have shell access.
    $ su - -s /bin/bash tomcat6
    $ sudo su - -s /bin/bash tomcat6
    

    Now cd to the directory where the clone Jenkins created is and use git config user.name and git config user.email to set the values.

    $ cd /srv/jenkins/jobs/project/workspace
    $ git config user.email "some@email.com"
    $ git config user.name "jenkins"
    

    When you are done, log off as the Jenkins user

Jenkins, GIT plugin and Windows

Installing the plugin itself works like a charm but configuring the system to work properly under Windows can be a be tricky. Let´s see the problems you may run into.

Configuring Jenkins to use OpenSSH bundled with msysgit Windows installer

By default, the Jenkins Windows installer sets up Jenkins to run as a service on Windows, which runs as the “Local System account”, NOT your user account. Since the “Local System account” does not have SSH keys or known_hosts set up, “git clone” will hang during the build.  It's possible to keep Jenkins running as the “Local System account” and clone repositories via SSH by making sure that the “Local System account” is set up with a properly configured .ssh directory (i.e. id_rsa, id_rsa.pub, AND known_hosts).  On my Windows 7 x64 box, this directory is C:\Windows\SysWOW64\config\systemprofile\.ssh

The first time you connect via SSH to a remote server, you would normally get prompted with the question "Are you sure you want to continue connecting (yes/no)?", which would populate the remote server info in your ~/.ssh/known_hosts.  Even with proper SSH keys set up for the Jenkins user, if you don't have a properly configured ~/.ssh/known_hosts, the build will still hang. 

A quick way to generate this known_hosts file is to copy your Jenkins build SSH keys into C:\Program Files (x86)\Git\.ssh (so that ssh.exe can find them), and run

 c:\>"C:\Program Files (x86)\Git\bin\ssh.exe" -T git@your.git.server

This will populate C:\Program Files (x86)\Git\.ssh\known_hosts and then you can just copy C:\Program Files (x86)\Git\.ssh to C:\Windows\SysWOW64\config\systemprofile\.ssh (the “Local System account” home).

For a more detailed tutorial, see http://computercamp-cdwilson-us.tumblr.com/post/48589650930/jenkins-git-clone-via-ssh-on-windows-7-x64

Added the server to your trusted list

First of all, if your system/user never connected to the git server, you will have to add the server to your list of trusted servers.
If you get something like this:

The authenticity of host 'GIT SERVER (127.0.0.1)' can't be established.
RSA key fingerprint is 41:d2:d9:31:76:7d:bd:0d:5e:3f:19:db:5d:34:4d:9d.
Are you sure you want to continue connecting (yes/no)? yes

or

The server's host key is not cached in the registry...

Find plink.exe on your system and run:

plink.exe yourgitserver.com

Answer Yes when prompt. You ignore the login part with CTRL+C.
Beware, this is user specific. SO if you run jenkins as user 'John', make sure you login as 'John' before running the previous command.

An alternative option is to add some entries in the registry to HKEY_USERS\.DEFAULT. You will typically run into this problem is you let Jenkins runn as "Local System" but try to add the key to your list while logged in with your user. The registry entries added for a specific user can be found here:

HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys

Setup your environment variables

General hint: Avoid spaces in environment paths

Mainly, you will need:

  • GIT_HOME => Folder where your git.exe is located
  • HOME => The parent folder of the folder containing your SSH Keys (e.g If your keys are in C:\SSHKeys, set HOME to C:)
  • PATH => Add the folder where your plink.exe is located

Once this is done, make sure you restart your consoles and the jenkins service.

SSH Keys

You will need to generate your SSH keys. The public key will have to be added/installed on the server. Systems like Gitorious, Gitosis or Github make it easy: you will have to simply copy/paste your key. If you need to setup the authentication with a 'simple' server, look for 'authorized_keys' in this document http://www.eng.cam.ac.uk/help/jpmg/ssh/authorized_keys_howto.html

You can read this: http://help.github.com/win-set-up-git/ to see how to generate the keys.

One solution to avoid entering your password (the one you defined in the ssh key in the process above) is to use Pageant.exe. Visit the link below for more details: http://www.ualberta.ca/CNS/RESEARCH/LinuxClusters/pka-putty.html

Note:* future *integration with ssh-credentials-plugin could help

Some windows fun

If you did everything, you should now have a ~/.ssh folder (c:\Users\Bob\.ssh for instance) and this folder contains your keys.
At that point, you may even be able to manually (from the console), clone your repository but Jenkins keeps failing with something like this:

code 128: Cloning into C:\Program Files\Jenkins\jobs\PG3\workspace...
fatal: The remote end hung up unexpectedly

If you run into this issue, you may need to copy the id_rsa* files from your ~./.ssh to another folder.
Find your git.exe and check if there is an .ssh folder there. If so, copy ~./ssh/id_rsa* to this folder and try again.

Push notification from repository

To minimize the delay between a push and a build, it is recommended to set up the post-receive hook in the repository to poke Jenkins when a new commit is made. To do this, add the following line in your hooks/post-receive where "URL of the Git repository" is the fully URL you use to clone this repository.

curl http://yourserver/jenkins/git/notifyCommit?url=<URL of the Git repository>[&branches=branch1[,branch2]*][&sha1=<commit ID>]

This will scan all the jobs that's configured to check out the specified URL, the optional branches, and if they are also configured with polling, it'll immediately trigger the polling (and if that finds a change worth a build, a build will be triggered in turn.) We require the polling configuration on the job so that we only trigger jobs that are supposed to be kicked from changes in the source tree.

This allows a script to remain the same when jobs come and go in Jenkins. Or if you have multiple repositories under a single repository host application (such as Gitosis), you can share a single post-receive hook script with all the repositories. Finally, this URL doesn't require authentication even for secured Jenkins, because the server doesn't directly use anything that the client is sending. It runs polling to verify that there is a change, before it actually starts a build.

When successful, this will return the list of projects that it triggered polling as a response.

Commit ID is optional. If set, it will immediately trigger a build, without requirement to poll for changes. Benefits is that you then can have all push tested by jenkins, even when developers push at ~ same time.

Why Not JGit

As of 1.2.0, the Git plugin uses git-client-plugin for all Git low-level operation. git-client was extracted from git plugin 1.1.x code base, to ensure SoC and allow other plugins (gerrit, git-parameters...) to directly use and contribute to this one when needed.

The git-client plugin 1.0.4 used JGit by default, while still including the command line Git implementation as an alternate implementation.  Initial deployments of the JGit based plugin exposed a number of gaps in the JGit implementation.  Those gaps need to be resolved in the JGit implementation before it can be used as the default implementation. Beginning wiht git-client-plugin 1.0.5, the command line implementation is the default implementation.

The git-client-plugin provides both command line and JGit implementations for the GitClient interface. Using command line demonstrated (based on large git plugin issue list) to be fragile : running an external process any time some git repository interaction is required introduces file and process leaks, filesystem locks, etc. It's highly system dependent and require user to install and configure adequate tools on all build slaves. It's based on parsing command output, and as such can be broken by any git cli update - legacy code already check git-cli version to detect which option can be used. Once the JGit functionality gaps are closed, we consider JGit will be the way to go. If you want to experiment with the JGit implementation, either configure JGit as an available git installation from the "Manage Jenkins" page, or run Jenkins with -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=false (same for slaves).

Advanced Features

Using Git, Jenkins and pre-build branch merging

Continuous Integration tools such as Jenkins are useful on projects as they give users early indication that a particular codebase is 'unstable' - and that if a developer checks it out, there will be trouble ahead (they won't be able to work on their own code, because someone else has broken something).

Unfortunately, by the time the build completes, this is often too late (particularly if the build cycle time is very long), as a developer has updated their working copy to the latest, unstable code in the repository and has begun work.

This can lead to the code base remaining unstable as developers tread on each others toes steadily fixing one thing, but breaking something else.

Some environments (e.g. TeamCity) attempt to fix this by making commits into SVN only 'really' happen once they have been tested. These kinds of 'delayed-commits' are problematic, because local SCM tools assume that commits will be immediately available, which can confuse them. In many ways this mechanism is a hack to get around the fact that branch management in SVN is very heavyweight.

Fortunately, with GIT and Jenkins, you can achieve the same 'stable branches' with minimal effort.

Set up your Jenkins project, and leave the 'branch' field in the Git SCM blank. This will cause Jenkins to consider any change on any branch for building.

Next, pick a particular branch name as the integration target in the 'Advanced' section - (e.g. 'master', or 'stable'), and select 'Merge before build'.

Select 'Push GIT tags back to origin repository' from the post-build actions (this is required to update your centralised git repo with the results of the build).

Now, developers should never commit directly to your integration branch (the 'master' or 'stable'). Instead, they should either use feature branches, or create new remote branches on commit (e.g : "git push origin HEAD:refs/heads/myNewFeature"). You could also set up your GIT repository to only accept commits onto the integration branch from Jenkins.

You're done. Commits should now be automatically merged with the integration branch (they will fail if they do not merge cleanly), and built. If the build succeeds, the result of the merge will be pushed back to the remote git repository.

Using Extra Repositories

Since GIT is a Distributed SCM, it is possible in the Advanced section to specify multiple repositories. You may wish to do this to, for example, pull all in-progress work from individual developers machines, and pre-test them before they are committed to a centralised repository - this way developers may get an early warning that a branch in progress may not be stable.

The GIT plugin will make reasonable attempts to try and pull submodule states from distributed repositories, with the proviso that this feature is not currently well supported within GIT itself.

Autogenerate submodule configurations

A common development pattern for many users is the use of a 'superproject' that aggregates a number of submodules. For example, ProjectA may have ComponentA, ComponentB and ComponentC. ComponentA is a shared library, and is set to use a particular revision (maybe on a branch called 'ProjectA' in case there are any changes). Usually, any changes to the project configuration require a commit to the ProjectA superproject.

However - there could be other changes happening on other branches of ComponentA (say to the development of the next version). Without someone generating commits into ProjectA to test these, any regressions or incompatibilities may be missed.

The autogenerate submodule configurations feature will create commits into ProjectA for all possible combinations of the branches present in the submodules that the project uses.

Recursive submodules

The GIT plugin supports repositories with submodules which in turn have submodules themselves. This must be turned on though: in Job Configuration -> Section Source Code Management, Git -> Advanced Button (under Branches to build) -> Recursively update submodules.

Environment variables

The git plugin sets several environment variables you can use in your scripts:

  • GIT_COMMIT - SHA of the current
  • GIT_BRANCH - Name of the branch currently being used, e.g. "master" or "origin/foo"
  • GIT_PREVIOUS_COMMIT - SHA of the previous built commit from the same branch (the current SHA on first build in branch)
  • GIT_URL - Repository remote URL
  • GIT_URL_N - Repository remote URLs when there are more than 1 remotes, e.g. GIT_URL_1, GIT_URL_2
  • GIT_AUTHOR_EMAIL - Committer/Author Email
  • GIT_COMMITTER_EMAIL - Committer/Author Email

Changelog

Also see long term plan

Version 2.2.1 (Apr 12, 2014)

  •   Allow clean before checkout (issue #22510)
  •   Do not append trailing slash to most repository browser URL's (issue #22342)
  •   Fix null pointer exception in git polling with inverse build chooser (issue #22053)

Version 2.2.0 (Apr 4, 2014)

  •   Add optional submodule remote tracking if git version newer than 1.8.2 (issue #19468)
  •   Update to JGit 3.3.1
  •   Fix javadoc warnings

Version 2.1.0 (Mar 31, 2014)

  •   support sparse checkout if git version newer than 1.8.2 (issue #21809)
  •   improve performance when many branches are in the repository (issue #5724)
  •   retain git browser URL when saving job configuration (issue #22064)
  •   resolve tags which contain slashes (issue #21952)

Version 2.0.4 (??? ??, 2014)

  •   ??? (tbd)

Version 2.0.3 (Feb 21, 2014)

Version 2.0.2 (Feb 20, 2014)

  •   option to configure timeout on major git operations (clone, fetch)
  •   locks are considered a retryable failure
  •   notifyCommit now accept a sha1 - make commit hook design simpler and more efficient (no poll required)
  •   extend branch specifier (issue #17417) and git repository URL
  •  Better support for branches with "/" in name (issue #14026)
  •  Improve backward compatibility (issue #20861)

Version 2.0.1 (Jan 8, 2014)

  •  Use git-credentials-store so http credentials don't appear in workspace (issue #20318)
  •  Prune branch during fetch (issue #20258)
  •  Fix migration for 1.x skiptag option (issue #20561)
  •  Enforce Refsepc configuration after clone (issue #20502)

Version 2.0 (Oct 22, 2013) - just in time for JUC :P

  •  Refactored git plugin for UI to keep clean. Most exotic features now are isolated in Extensions, that is the recommended way to introduce new features
  •  Introduce support for credentials (both ssh and username/password) based on credentials plugin

Version 1.5.0 (Aug 28, 2013)

  • Additional environmental values available to git notes
  • Extension point for other plugin to receive commit notifications
  • Support promoted builds plugin (passing GitRevisionParameter)
  • Do not re-use last build's environment for remote polling (issue #14321)
  • Fixed variable expansion during polling (issue #7411)
  • Added Phabricator and Kiln Harmony repository browsers, fixed GitLab URLs

Version 1.4.0 (May 13, 2013)

  •  Avoid spaces in tag name, rejected by JGit (issue #17195)
  •  Force UTF-8 encoding to read changelog file (issue #6203)
  •  Retry build if SCM retry is configured (issue #14575)
  •  Allow merge results to push from slave nodes, not just from master node (issue #16941)

Version 1.3.0 (March 12, 2013)

  • Fix a regression fetching from multiple remote repositories (issue #16914)
  • Fix stackoverflow recursive invocation error caused by MailAddressResolver (issue #16849)
  • Fix invalid id computing merge changelog (issue #16888)
  • Fix lock on repository files (issue #12188)
  • use default git installation if none matches (issue #17013).
  • Expand reference parameter when set with variables
  • Expose GIT_URL environment variable (issue #16684)
  • Branch can be set by a regexp, starting with a colon (pull request #138)

Version 1.2.0 (February 20, 2013)

  • move git client related stuff into Git Client plugin
  • double checked backward compatibility with gerrit, git-parameter and cloudbees validated-merge plugins.

Version 1.1.29 (February 17, 2013)

  • fix a regression that breaks jenkins remoting
  • restore BuildChooser API signature, that introduced issue #16851

Version 1.1.27 (February 17, 2013)

  • add version field to support new GitLab URL-scheme
  • Trim branch name - a valid branch name does not begin or end with whitespace. (issue #15235)
  • set changeSet.kind to "git"
  • Avoid some calls to "git show"
  • Fix checking for an email address (issue #16453)
  • update Git logo icon
  • Pass combineCommits to action (issue #15160)
  • expose previous built commit from same branch as GIT_PREVIOUS_COMMIT
  • re-schedule project when multiple candidate revisions are left
  • expand parameters in the remote branch name of merge options
GitAPI cleanup

Long term plan is to replace GitAPI cli-based implementation with a pure java (JGit) one, so that plugin is not system dependent.

  • move git-plugin specific logic in GitSCM, have GitAPI implementation handle git client stuff only
  • removed unused methods
  • create unit test suite for GitAPI
  • create alternate GitAPI implementation based on JGit

Version 1.1.26 (November 13, 2012)

  • git polling mechanism can have build in infinite loop (issue #15803)

Version 1.1.25 (October 13, 2012)

  • Do "git reset" when we do "git clean" on git submodules (pull #100)
  • NullPointerException during tag publishing (issue #15391)
  • Adds RhodeCode support (issue #15420)
  • Improved the BuildChooser extension point for other plugins.

Version 1.1.24 (September 27, 2012)

  • Shorten build data display name issue #15048
  • Use correct refspec when fetching submodules issue #8149
  • Allow a message to be associated with a tag created by the plugin

Version 1.1.23 (September 3, 2012)

  • Improve changelog parsing for merge targets
  • prevent process to hang when git waits for user to interactively provide credentials
  • option to create a shallow clone to reduce network usage cloning large git repositories
  • option to use committer/author email as ID in jenkins user database when parsing changelog (needed for openID / SSO integration)
  • validate repository URL on job configuration

Version 1.1.22 (August 8, 2012)

  • Fix regression for fully qualified branch name (REPOSITORY/BRANCH) issue #14480
  • Add support for variable expansion on branch spec (not just job parameters) issue #8563
  • Use master environment, not last build node, for fast remote polling issue #14321
  • run reset --hard on clean to take care of any local artifact
  • normalize maven repository ID issue #14443

Version 1.1.21 (July 10, 2012)

  • Fixed support for "/" in branches names (issue #14026)
  • Fixed issue on windows+msysgit to escape "^" on git command line (issue #13007)

Version 1.1.20 (June 25, 2012)

Version 1.1.19 (June 8, 2012)

  • restore GitAPI constructor for backward compatibility (issue #12025)
  • CGit browser support (issue #6963).
  • Handle special meaning of some charactes on Windows (issue #13007)
  • fixed java.lang.NoSuchMethodError: java/lang/String.isEmpty() (issue #13993).
  • Git icon(git-48x48.png) missing in job page. (issue #13413).
  • Git "Tag to push" should trim whitespace (issue #13550).

Version 1.1.18 (released April 27, 2012)

  • Loosened the repository matching algorithm for the push notification to better work with a repository with multiple access protocols.

Version 1.1.17 (released April 9, 2012)

  • Fixed NPE in compareRemoteRevisionWith (issue #10880)
  • Improved the caching of static resources
  • notifyCommit endpoint now accept a comma delimited list of affected branches. Only the build(s) that match those branches will be triggered

Version 1.1.16 (released February 28, 2012)

Version 1.1.15 (released December 27, 2011)

  • Fixed a bug where the push notification didn't work with read-protected projects. (issue #12022)
  • Improved the handling of disabled projects in the push notification.

Version 1.1.14 (released November 30, 2011)

Version 1.1.13 (released November 24, 2011)

  • option to ignore submodules completely (issue #6658)
  • support FishEye scm browser (issue #7849)
  • inverse choosing strategy to select all branches except for those specified (pull request #45)
  • option to clone from a reference repository
  • fix databinding bug (issue #9914)
  • action to tag a build, similar to subversion plugin feature

Version 1.1.12 (released August 5, 2011)

  • When choosing the branch to build, Jenkins will pick up the oldest branch to induce fairness in the scheduling. (it looks at the timestamp of the tip of the branch.)
  • Git now polls without needing a workspace (issue #10131)
  • Fixed the "no remote from branch name" problem (issue #10060)

Version 1.1.11 (released July 22, 2011)

Version 1.1.10 (released July 15, 2011)

  • Merge options persist properly now. (issue #10270)
  • Fixed NPE in PreBuildMergeOptions when using REST API. (issue #9843)
  • Global config name/email handle whitespace properly. (issue #10272, issue #9566)
  • Improved memory handling of "git whatchanged". (issue #8365)
  • Excluded regions should now work with multiple commit changesets. (issue #8342)
  • ViewGit support added. (issue #5163)
  • Fixed NPE when validating remote for publisher. (issue #9971)
  • Tool selection persists now. (issue #9765)
  • Remote branch pruning now happens after fetch, to make sure all remotes are defined. (issue #10348)

Version 1.1.9 (released May 16, 2011)

  • Don't strip off interesting stuff from branch names in token macro (issue #9510)
  • Changes to serialization to support working with the MultiSCM plugin and general cleanliness. (github pull request)
  • Check to be sure remote actually exists in local repo before running "git remote prune" against it. (issue #9661)
  • Eliminate a problem with NPEs on git config user.name/user.email usage on upgrades. (issue #9702)
  • Add a check for git executable version as 1.7 or greater before using --progress on git clone calls. (issue #9635)

Version 1.1.8 (released May 6, 2011)

  • Re-release of 1.1.7 to deal with forked version of plugin having already released with same groupId/artifactId/version as our 1.1.7 release, thereby breaking things.

Version 1.1.7 (released May 4, 2011)

  • GIT_COMMIT environment variable now available in builds. (issue #9253)
  • Improved wording of error message when no revision is found to build. (issue #9339)
  • Added "--progress" to git clone call. (issue #9168)
  • Underlying error actually shown when git fetch fails. (issue #9052)
  • git config options for user.name and user.email now save properly. (issue #9071)
  • Properly handle empty string for branch when branch is parameterized. (issue #8656)
  • If no Jenkins user is found for a commit's user.name value, strip the username from "username@domain.com" from the user.email value and use that instead. (issue #9016)

Version 1.1.6 (released Mar 8, 2011)

  • Fix for warning stacktrace if paramaterized trigger plugin was not installed.
  • No longer try to generate complete history as changelog if previous build's SHA1 no longer exists in repository. (issue #8853)
  • Fixed bug causing "Firstname Lastname@domain.com" to be used as email address for users. (issue #7156)
  • Passwords should now be properly used in https URLs. (issue #3807)
  • Exposed a few token macros

Version 1.1.5 (released Feb 14, 2011)

  • Added an extension for Parameterized Trigger Plugin to allow Git SHA1 of the current build to be passed to downstream builds (so that they can act on the exact same commit.)
  • Allowed optional disabling of internal tagging (issue #5676)
  • If specified, use configured values for user.email and user.name (issue #2754)
  • Removed obsolete/unused wipe out workspace option and defunct Gerrit build chooser.
  • Rebranded to Jenkins!

Version 1.1.4 (released December 4, 2010)

  • For Matrix projects, push only at the end of the whole thing, not at the configuration build (issue #5005).
  • Switching between browsers does not function properly (issue #8210).
  • Implement support for Redmine as browser.

Version 1.1.3 (released November 8, 2010)

  • No changes except of updated version according to scm.

Version 1.1.2 (released November 8, 2010)

Version 1.1.1 (released November 5, 2010)

  • Improved logging for failures with git fetch.
  • Made sure .gitmodules is closed properly. (issue #7659)
  • Fixed issue with polling failing if the master has 0 executors. (issue #7547)
  • Modified Git publisher to run as late as possible in the post-build plugin order. (issue #7877)
  • Added optional call to "git remote prune" to prune obsolete local branches before build. (issue #7831)

Version 1.1 (released September 21, 2010)

  • Added ability for GitPublisher to only push if build succeeds. (issue #7176)
  • Fixed major bug with submodule behavior - making sure we don't try to fetch submodules until we've finished the initial clone. (issue #7258)
  • "Clean after checkout" wasn't invoked when pre-build merges were enabled. (issue #7276)
  • Form validation was missing for the GitPublisher tag and branch names, and an empty value was allowed for GitPublisher target repositories, leading to confusion. (issue #7277)
  • "Clean before build" will now run in submodules as well as root. (issue #7376)
  • When polling, Hudson-configured environment variables were not being used. (issue #7411)
  • Modifications to BuildData to deal with Hudson no longer serializing null keys. (issue #7446)
  • Support for --recursive option to submodule commands. (issue #6258)

Version 1.0.1 (released August 9, 2010)

  • Fixed submodules support - was broken by issue #6902 fix. (issue #7141)
  • Switched "Recent Changes" list for a project to count changes per build, rather than using revision as if it were a number. (issue #7154)
  • Stopped putting problematic slash at end of GitWeb URL. (issue #7020)

Version 1.0 (released July 29, 2010)

  • Added support for Github as a repository browser.
  • Added support for optionally putting source in a subdirectory of the workspace (issue #6357)
  • If all repository fetches fail, fail the build. (issue #6902)
  • Improved logging of git command execution errors (issue #6330)
  • Basic support for excluded regions and excluded users in polling added (issue #4556)
  • Support for optionally checking out to a local branch, rather than detached HEAD (issue #6856)
  • Revamped GitPublisher to allow for pushing tags to remotes and pushing to remote branches, as well as existing push of merge results. (issue #5371)

Version 0.9.2 (released June 22, 2010)

  • Fixed major bug in BuildChooser default selection and serialization (issue #6827)

Version 0.9.1 (released June 22, 2010)

  • Dramatic improvement in changelog generation, thanks to a switch to use "git whatchanged" (issue #6781)

Version 0.9 (released June 17, 2010)

  • Improved support for BuildChooser as an extension point - other plugins can now implement their own BuildChoosers and have them automatically show up as an option in Git configuration when installed.
  • Options added for wiping out the workspace before the build begins (this option may be removed), and for using commit authors as the Hudson changelog entry author, rather than the committers, the default behavior.

Version 0.8.2

  • Support for Gerrit plugin.
  • Support for different build choosers.

Version 0.7.3

FIXME this changelog entry is incomplete! Please give me some love!

  • Fixed issue #2931, git tag freezing job execution (jbq)
  • Improve log messages (jbq)
  • Use build listener to report messages when pushing tags to origin (jbq)
  • Fixed issue #2762, fail to clone a repository on Windows (jbq)

Version 0.5

  • Fix git plugin which was very broken when running on a remote server (magnayn)
  • Fix NPE in GitChangeLogParser upon project's first build (jbq)
  • Change workspace to a FilePath in GitAPI (jbq)
  • Use git rev-list once instead of invoking git rev-parse indefinitely to find last build, see issue #2469: GIT plugin very slow (jbq)
  • Handle null-value of the repositories field to ensure backwards-compatibility with version 0.3,
    ie when the project configuration is missing the <repositories/> XML element (jbq)
  • Improve error handling in revParse() (jbq)
  • Fix handling of the "branch" configuration parameter (jbq)
  • Improve tag handling, use show-ref instead of rev-parse to resolve the tag reference (jbq)
  • Fix issue #2675, Git fails on remote slaves (jbq)

Version 0.4 (never released)

  • Allow multiple GIT repositories to be specified (magnayn)
  • Allow submodule configurations to be generated on the fly (magnayn)
  • Avoid infinite loops when git doesn't contains tags (david_calavera)
  • Don't do a log of the entire branch if it's never been built (magnayn)

Version 0.3

  • Add support for pre-build branch merges

Version 0.2

  • Improve handling of git repositories (use local tags to identify up to date versions rather than the wc HEAD)
  • Don't have to specify a branch, in which case all branches are examined for changes and built
  • Includes a publisher which can be used to push build success/failure tags back up to the upstream repository

Version 0.1

  • Initial Release

Labels

Edit
plugin-scm plugin-scm Delete
token-producer token-producer Delete
parameterized-trigger-contributer parameterized-trigger-contributer Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment