The purpose of this article is to detail for users the steps necessary to integrate different versions of Git with Kiln and FogBugz On Demand, including GitHub, GitHub Enterprise, and Generic Git.
- Using Git with Kiln
- Integrating GitHub with FogBugz On Demand
- Integrating GitHub Enterprise with FogBugz On Demand
- Integrating Generic Git with FogBugz On Demand
Using Git with Kiln
Kiln, our best-in-class DVCS hosting solution, supports Git as well as Mercurial! To take advantage of what Git has to offer, do the following:
- Log in to your existing Kiln On Demand account.
- Navigate to a repository.
- Change your view between Mercurial and Git.
If you don’t have a Kiln On Demand account, you can sign up for a fourteen-day free trial and check it out.
Integrating GitHub with FogBugz On Demand
GitHub is great. FogBugz is great. What could be even better? How about integrating them! FogBugz can be notified by GitHub WebHooks whenever an incoming changeset comment mentions a case. Let’s get an integration set up.
- In FogBugz, go to the Menu icon > Source Control.
- On the Source Control page, create a new repository by clicking Look no further! within the GitHub banner.
- On the GitHub Repositories page, click Add New Repository.
- Select Authorize FogBugz to give the FogBugz application access to your GitHub repositories. This step takes you to a GitHub page to complete the authorization process, and once this is complete, you are returned to the next step in FogBugz.
Note: Make sure you are logged in with the correct GitHub Account to see the repositories you want to add.
- Select the checkboxes for the repositories you wish to integrate, and then select Add repositories.
- Your selections are confirmed. Select Done, and the new repository is listed on the next screen.
- Now you can refer to your FogBugz cases in your GitHub commits by adding case <number> in the commit message. Your cases now show your commits.
Integrating GitHub Enterprise with FogBugz On Demand
For self-service integration between GitHub Enterprise and FogBugz On Demand, follow the instructions on how to integrate GitHub Enterprise Integration with Manuscript On-Demand in Source Control, substituting your GitHub Enterprise URLs as appropriate. It is technically possible to get the fancy in-line integration up and running with a little bit of work “under the hood.” Transplant the GitHub configuration to your Enterprise installation, and we’ll help clean up any loose ends on the FogBugz side. Let us know if you are interested, and we’ll get you hooked up!
Integrating Generic Git with FogBugz On Demand
Integrating Git with FogBugz On Demand is easier than ever before, but keep in mind that for non-GitHub git, we do not currently include hook scripts.
- To begin configuring Git integration, navigate to Source Control.
- Choose Create New Repository.
- On the New Repository screen, select Git, and give your repository reference a Name.
- Click Next to proceed.
- Click on the Generic Git tab.
- Download both of the listed scripts and place them in the .git/hooks directory of your master repository. Make sure these scripts are executable by the git daemon.
Optional: You can configure the path to git-instaweb to enable links to logs and diffs using git-instaweb. Otherwise, you can disable this feature by unchecking Enable links to logs and diffs using git-instaweb.
- Click OK to complete the process.
Using the Integration
When you commit changes to Git, include the keywords “BugzID: XYZ” where XYZ is a case number in your commit message, and the configuration you just set up links the case to the changeset in Git.
|Question 1||Are the commit message keywords case sensitive?|
|Answer 1||No. You can use mixed case in your commit messages.|
|Question 2||What are the differences between GitHub Issues and those experienced with FogBugz?|
|Answer 2||Here are some details about the differences between FogBugz and GitHub Issues.|