Through rtyler: http://github.com/stephenh/git-central/blob/master/server/post-receive-hudson automates the set up of a Hudson job whenever a new branch is created. Nice.

How do I build a specific revision? I used to be able to specify a build should use SHA1-ID, like build origin/bdbbfc3f0e9c57fbeff89de2ad7ca308a168575e and it would work.  This is necessary for reproducibility.

Has this changed? How do I do this now?

I wrote a tutorial on getting hudson to work with git and grails.  It includes all the information necessary to set up an integration server using git and hudson even if you aren't interested in grails development:

http://www.electricsenator.net/2009/10/03/1254618530821.html

Is it possible to use credentials when accessing a git repository? Or certificates?

Thanks,
Graeme

Is there any way to get the git plugin to checkout ref names instead of the sha's associated with remote refs? Not being on a branch in the course of a build is causing issues (for at least two of us) in conjunction with the M2 Release Plugin:

Can’t get automated release working with Hudson + Git + Maven Release Plugin

I can't get Hudson to merge into the master branch. It always ends up in *no branch, which is no good to me as I want to push master to another remote repo as a deploy.
I've set the following:
refspec: +refs/heads/master:refs/remotes/origin/master
branch to build: */master
branch to merge to: master

The Git logs show it fetching the latest, then for some reason checking out the previous version with the sha, which puts it into *no branch. Then it does a git merge with the latest, still on *no branch. I've included the logs below.

I don't think this is the correct behavior given that I specify that I want to merge to the master branch. Thoughts? Bug?

Git logs from hudson:
git fetch /home/git/repositories/my_repo.git +refs/heads/master:refs/remotes/origin/master
git ls-tree HEAD
git rev-parse master
git checkout -f old_rev_sha here's where it switches branches
git merge new_rev_sha

Problems with new 0.8 version under windows.

It looks very good and the new information about changed files is great but scm polling doesn't work anymore

Is there an inconsistency here? This page says 0.8 is the Latest Release, but the download link to the .hpi file is pointing at 0.7.3.

What is the download link to the 0.8 hpi please, as I need to archive this file for static installation at my site.

Hi,

I have a problem with latest Hudson v1.352 and Git plugin v0.8.1.
After fetching successfully Git sources - Maven fails with NPE

java.lang.NullPointerException
	at java.util.Hashtable.put(Hashtable.java:394)
	at java.util.Hashtable.putAll(Hashtable.java:466)
	at hudson.maven.MavenBuilder.call(MavenBuilder.java:156)
	at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:688)
	at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:632)
	at hudson.remoting.UserRequest.perform(UserRequest.java:114)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:270)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)

Here's the full log and job's configuration

Git plugin passes null value for GIT_BRANCH environment variable,
which later fails in MavenBuilder.java:156 when Maven plugin calls
System.getProperties().putAll(systemProps)

Here's a debugger screenshot.

I'm hoping this is the right place to post this question...  It looks like the Git plugin simply issues a git fetch origin master (or something reasonably similar).  I want to force a clean before fetching.  specifically "git -fx clean"  Does anyone know how to make this happen?  I could add this to the build commands, but that seems a little wrong.

Help!

-Mark

This page should probably mention that the Git plugin relies on a recent version of the Git binaries (at least 1.7?).

Same problem here with builds always starting from a detached HEAD. I'm using the most recent version of the plugin, 0.8.3.

My config is:

URL of repository: git://github.com/simplegeo/libmemcached.git
Name of repository: origin
Refspec: +refs/heads/*:refs/remotes/origin/*

Branches to build: master

Merge before build: Yes
Name of repository: origin
Branch to merge to: master

Clean after checkout: Yes
Choosing strategy: Default
Repository browser: (Auto)

These are the git commands that get run:

Checkout:libmemcached-test / /home/pubhudsonslave/workspace/libmemcached-test - hudson.remoting.Channel@581ea2:pubhudsonslave
Using strategy: Default
Last Built Revision: Revision 13e70eabe93822d0ce7fceee6ebcbbd490b19a76 (origin/master)
Checkout:libmemcached-test / /home/pubhudsonslave/workspace/libmemcached-test - hudson.remoting.LocalChannel@135c7da7
GitAPI created
Fetching changes from the remote Git repository
Fetching upstream changes from git://github.com/simplegeo/libmemcached.git
[libmemcached-test] $ git fetch -t git://github.com/simplegeo/libmemcached.git +refs/heads/*:refs/remotes/origin/*
[libmemcached-test] $ git ls-tree HEAD
[libmemcached-test] $ git tag -l master
[libmemcached-test] $ git rev-parse origin/master
Commencing build of Revision 13e70eabe93822d0ce7fceee6ebcbbd490b19a76 (origin/master)
GitAPI created
Checking out Revision 13e70eabe93822d0ce7fceee6ebcbbd490b19a76 (origin/master)
[libmemcached-test] $ git checkout -f 13e70eabe93822d0ce7fceee6ebcbbd490b19a76
[libmemcached-test] $ git tag -a -f -m "Hudson Build #7" hudson-libmemcached-test-7
Recording changes in branch origin/master
[libmemcached-test] $ git log --pretty=format:%H 13e70eabe93822d0ce7fceee6ebcbbd490b19a76..13e70eabe93822d0ce7fceee6ebcbbd490b19a76
Cleaning workspace
[libmemcached-test] $ git clean -fdx
Finished: SUCCESS

It's not merging anything, and it's still checking out a SHA-1 instead of a symbolic branch name. What gives?

I'm trying to figure out how the tags generated by the plugin for each build are pushed back to the origin repository.

The text above mentions an option called 'Push GIT tags back to origin repository' but I'm not able to find it.

So how do I get the plugin pushing the tags for each build to the upstream repo?

Folks, I'm experiencing problems setting up the GIT Plugin on a Debian system using a SSH key for authentication and was hoping somebody has had some experience with this setup who could offer some pointers.

I believe the problem is that it fails to find the key and thus present it to the GIT server. I've installed a valid key into the /usr/share/tomcat5.5/.ssh directory which is the home of the tomcat55 user but it fails with a ssh-askpass error.

Now I'm guessing that the process is running as the tomcat55 user but I could be wrong as looking at the logs below you can see that it is attempting to fetch to the /home/hudson directory. What's confusing about this is that the system does not have a user 'hudson' and in the System Information section of the web interface the enveronment looks as though it's running as the root user.

Here's the log output;

------------------
Started by user ITDude
Checkout:workspace / /home/hudson/jobs/TestHudson/workspace - hudson.remoting.LocalChannel@f74f6ef
Using strategy: Default
Checkout:workspace / /home/hudson/jobs/TestHudson/workspace - hudson.remoting.LocalChannel@f74f6ef
GitAPI created
Fetching changes from the remote Git repository
Fetching upstream changes from git@git.mycomp.com:test_hudson.git
[workspace] $ /usr/bin/git fetch -t git@git.mycomp.com:test_hudson.git +refs/heads/:refs/remotes/origin/
No protocol specified

(ssh-askpass:13369): Gtk-WARNING **: cannot open display: :0.0
Permission denied, please try again.
No protocol specified

(ssh-askpass:13370): Gtk-WARNING **: cannot open display: :0.0
Permission denied, please try again.
No protocol specified

(ssh-askpass:13371): Gtk-WARNING **: cannot open display: :0.0
Permission denied (publickey,password).
fatal: The remote end hung up unexpectedly
ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway
ERROR: Nothing to do
Finished: FAILURE
========================

The key is definitely valid as I've tested it with a manual connection.

Hello,

I'm having difficulties getting the git plugin to fetch from the repository. In the job's configuration I have provided:

URL of repository: git@git.mydomain.com:test_hudson.git

• which as far as I know is correct.

Name of repository: origin/master

• I have two choices. My repository is remote and according to Git Extensions on my Windows machine where I am pushing code to the central repository the repository is either origin/HEAD or origin/master - I have tried both.

Refspec: I leave this blank and it generates the following: +refs/heads/:refs/remotes/origin/master/

I have also provided the Branches to build: master

I have tried many different combinations of settings, and each one gives a different error message, but none of them are ever getting to the point where Ant builds my simple Java project. On the above settings, I get the following log:

***

Started by user daleh
Checkout:workspace / /home/hudson/jobs/TestHudson/workspace - hudson.remoting.LocalChannel@3219ab8d
Using strategy: Default
Checkout:workspace / /home/hudson/jobs/TestHudson/workspace - hudson.remoting.LocalChannel@3219ab8d
GitAPI created
Fetching changes from the remote Git repository
Fetching upstream changes from git@git.mydomain.com:test_hudson.git
[workspace] $ /usr/bin/git fetch -t git@git.mydomain.com:test_hudson.git +refs/heads/:refs/remotes/origin/master/
error: unable to resolve reference refs/remotes/origin/master/master: Not a directory
From git@git.mydomain.com:test_hudson
! [new branch] master -> origin/master/master (unable to update local ref)
error: some local refs could not be updated; try running
'git remote prune git@git.mydomain.com:test_hudson.git' to remove any old, conflicting branches
ERROR: Problem fetching from origin/master / origin/master - could be unavailable. Continuing anyway
[workspace] $ /usr/bin/git tag -l master
[workspace] $ /usr/bin/git rev-parse origin/master/master
ERROR: Nothing to do
Finished: FAILURE

***

As for needing to remove any "old conflicting branches", I have none. This is a simple project with no conflicting branches.

Thanks in advance for any help provided

Hello,
I have repoA and repoB, and i want clone repoA to directory for example workspace/myJob/A and clone repoB to workspace/myJob/B. Is it possible with this plugin ?

Having Serious Submodule Problems. I confess that I don't understand what the documentation above about automatic submodule handling is trying to convey about what Hudson is doing, but whatever it is, it seems to be wrong. I'm content to do the git submodule init / git submodule update myself if necessary. Log below; can you please help? Thanks!

Started by user dave
Checkout:workspace / /var/lib/hudson/jobs/Boost/workspace - hudson.remoting.LocalChannel@3faa7a6a
Using strategy: Default
Last Built Revision: Revision 9fc9270750b81ec49fb96ee7b37fde5547da67c7 (origin/master)
Checkout:workspace / /var/lib/hudson/jobs/Boost/workspace - hudson.remoting.LocalChannel@3faa7a6a
GitAPI created
Cloning the remote Git repository
Cloning repository origin
$ git clone -o origin git://gitorious.org/ryppl/boost.git /var/lib/hudson/jobs/Boost/workspace
Fetching upstream changes from git://gitorious.org/ryppl/boost.git
[workspace] $ git fetch -t git://gitorious.org/ryppl/boost.git +refs/heads/:refs/remotes/origin/
[workspace] $ git ls-tree HEAD
GitAPI created
Fetching upstream changes from git://gitorious.org/ryppl/boost.git/cmake/.git
[cmake] $ git fetch -t git://gitorious.org/ryppl/boost.git/cmake/.git +refs/heads/:refs/remotes/origin/
fatal: protocol error: expected sha/ref, got '
----------------------------------------------
Cannot find repository /ryppl/boost.git/cmake/.git
----------------------------------------------'
ERROR: Problem fetching from origin - could be unavailable. Continuing anyway
[workspace] $ git submodule init
[workspace] $ git submodule update
[workspace] $ git tag -l master
[workspace] $ git rev-parse origin/master
Commencing build of Revision 9fc9270750b81ec49fb96ee7b37fde5547da67c7 (origin/master)
GitAPI created
Checking out Revision 9fc9270750b81ec49fb96ee7b37fde5547da67c7 (origin/master)
[workspace] $ git checkout -f 9fc9270750b81ec49fb96ee7b37fde5547da67c7
[workspace] $ git submodule init
[workspace] $ git submodule sync
Fetching upstream changes from git://gitorious.org/ryppl/boost.git
[workspace] $ git fetch -t git://gitorious.org/ryppl/boost.git +refs/heads/:refs/remotes/origin/
[workspace] $ git ls-tree HEAD
GitAPI created
Fetching upstream changes from git://gitorious.org/ryppl/boost.git/cmake/.git
[cmake] $ git fetch -t git://gitorious.org/ryppl/boost.git/cmake/.git +refs/heads/:refs/remotes/origin/
fatal: protocol error: expected sha/ref, got '
----------------------------------------------
Cannot find repository /ryppl/boost.git/cmake/.git
----------------------------------------------'
ERROR: Problem fetching from origin - could be unavailable. Continuing anyway
[workspace] $ git submodule update
[workspace] $ git tag -a -f -m "Hudson Build #4" hudson-Boost-4
Recording changes in branch origin/master
[workspace] $ git whatchanged --no-abbrev -M --pretty=raw 9fc9270750b81ec49fb96ee7b37fde5547da67c7..9fc9270750b81ec49fb96ee7b37fde5547da67c7
Triggering default
Finished: FAILURE

There is no included region feature for GIT. If there are some few regions to be participated in the build I think its not a good idea to have so many excluded regions to be listed. Included region will be doing better in this case.