Set up the Lighthouse service

Deprecated

Creation of new service integrations has been deprecated in favor of Bitbucket Cloud's webhooks, Connect integration framework, and email notifications.

With this service, you can integrate Bitbucket Cloud with Lighthouse, a simple issue tracking system. If you are having trouble with the service, see Troubleshooting Bitbucket services.

Setting Up your Project at Lighthouse

  1. Create a project in Lighthouse corresponding to the project you are tracking at Bitbucket.
  2. Access your Lighthouse profile page by clicking on your name next to the 'sign out' link.
  3. Select an account from the Create an API Token dropdown menu on the right-hand side of the page.
  4. Give your token a label (anything you want).
  5. Make sure you give it Full access to the project you want to integrate.
  6. 作成」ボタンをクリックします。
  7. Copy the API token created (just the token).

Setting up the service at Bitbucket

 You must have administrative access on a repository to add this service.

  1. Go to the repository's settings.
  2. Click Services in the left-hand navigation.
    The Services page appears.
  3. Select the Lighthouse service from the services dropdown.
  4. Click Add service.
    A new section appears for the Lighthouse service.
  5. 以下の情報を入力します:

    Project Id
    Enter the numeric ID for your project. You can get it from your project URL at Lighthouse.
    For example, let's say your Lighthouse project URL is this:
    XXXXX.lighthouseapp.com/projects/00000-yourproject/overview
    In this case, 00000 would be your Project ID.
    API Key
    Enter the API token you have created at Lighthouse (see above).
    Subdomain
    Enter your Lighthouse account name.
    For example, let's say your Lighthouse project URL is this:
    XXXXX.lighthouseapp.com/projects/00000-yourproject/overview
    In this case, XXXXX would be your subdomain.

  6. Press Save.

Posting Changes to Lighthouse

Now you can easily associate your commits to tickets at Lighthouse, using a special syntax in your commit messages. Here are some examples.

Let's say you have a ticket at lighthouse regarding a login problem and this ticket has ID '22'.

When you commit changes regarding this ticket, you may use:

hg ci -m "Commit regarding that login problem. [#22]"

This will post this commit as a changeset inside your ticket #22.

Let's say you have resolved that ticket:

hg ci -m "Login problem resolved. [#22 state:resolved]"

This will automatically change the state of that ticket at Lighthouse.

You can chain many options in your commit, like this:

[#22 state:hold responsible:paul milestone:'My Milestone Name' tagged:nonspacedtag tagged:'a spaced tag' tagged:'multiple tags']

Summary of the options available:

  • state: Changes the ticket state.

    [#22 state:resolved]
    
  • responsible: Changes the responsible person for this ticket.

    [#22 responsible:lighthouse-username]
    
  • milestone: Sets this ticket into a milestone.

    [#22 milestone:'My Milestone']
    
  • tagged: Adds tags to the ticket. May be used multiple times.

    [#22 tagged:nonspacedtag tagged:'a tag with spaces']
最終更新日 2017 年 7 月 13 日

この翻訳に満足しましたか?

はい
いいえ
この記事についてのフィードバックを送信する

お探しの情報が見つかりませんか?

コミュニティへの質問

Powered by Confluence and Scroll Viewport.