Exploring SVN / GIT and Jenkins integration

Was working on creating a test SVN repository for testing purposes.
I have worked extensively with CVS before in my experience in HP enterprise services, but done limited work with SVN.

SVN is much better CM tool and offers a set of decent web interfaces and integrates well with apache.
Jenkins also supports GIT, which would be my next logical step.
Jenkins can do a lot integrating with a CM tool from doing old style deployment to distributing codes and scripts to different parts of a given system.
Jenkins has the ability to managed remote nodes and can even work with standard password authentication. handles all the overhead beautifully :)

Setting up GIT is similar to SVN.
Now following the below link to setup a GIT repository for testing.
http://git-scm.com/book/en/Git-on-the-Server-Setting-Up-the-Server

integrating git with Jenkins would work straight forward similar to SVN.

 

TC server JMX trap !

From: http://static.springsource.com/projects/tc-server/2.0/admin/htmlsingle/admin.html#manual



Warning: The value of the bind attribute of JmxSocketListener overrides the value of the java.rmi.server.hostname Java system property. This directly affects how names are bound in the RMI registries; by default, the names will be bound to localhost (127.0.0.1.) This in turn means that RMI clients running on a different host from the one hosting the tc Runtime instance will be unable to access the RMI objects because, from their perspective, the host name is incorrect. This is because, the host should be the name or IP address of the tc Runtime computer rather than localhost. When the tc Runtime instance starts, if it finds that the value of the bind attribute is different from or incompatible with the java.rmi.server.hostname Java system property, the instance will log a warning but will startup anyway and override the system property as described. If this causes problems in your particular environment, then you should change the value of the bind attribute to specify the actual hostname on which the tc Runtime runs rather than the default 127.0.0.1 value.


The above has cause me to work for 4 hours looping in circles !!!
Tomcat just rocks !!