ccnet.git.plugin¶ ↑

Source Control Plugin for CruiseControl.NET that talks to git.

configuration¶ ↑

minimal ccnet configuration¶ ↑

<sourcecontrol type="git">
      <repository>git@github.com:dogeth/ccnet.git.plugin.git</repository>
</sourcecontrol>

fully specified ccnet configuration¶ ↑

<sourcecontrol type="git">
      <repository>git@github.com:dogeth/ccnet.git.plugin.git</repository>
      <branch>master</branch>
      <autoGetSource>true</autoGetSource>
      <executable>git</executable>
      <tagOnSuccess>false</tagOnSuccess>
      <tagCommitMessage>ccnet build {0}</tagCommitMessage>
      <workingDirectory>c:\build\ccnet.git.plugin</workingDirectory>
      <timeout>60000</timeout>
</sourcecontrol>

Environment¶ ↑

Before even attempting to use this plugin, take note of the following

• Your path should include %ProgramFiles%Gitbin and %ProgramFiles%Gitcmd

• The HOME environment variable should be set to %USERPROFILE%

• You should be able to run git from a standard command prompt.

Things to do¶ ↑

• I’m not checking for multiple heads, like the mercurial source control class. Didn’t see that situation arising in our current git workflow so I didn’t bother.

• The position of each modification in the list is used as the ChangeNumber. WHen 1.5 comes around may be able to use the commit hash instead.

• The type of modification is used to store the commit hash. Should expand this to actual file information.

• Commit level modifications are used. Actual files changed in each commit are not published. Obviously something which could be implemented but have run out of time for the moment.

Credits¶ ↑

I took a lot of ideas from the following

• jira.public.thoughtworks.org/browse/CCNET-1188

• www.codeplex.com/TFSCCNetPlugin/

• ccnet source

I also got some great feedback from Xerxes Battiwalla, see his blog post on the matter at www.xerxesb.com/2009/getting-cruisecontrolnet-to-talk-to-git/

License¶ ↑

The MIT License

Copyright © 2009 Kevin Read

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.