changes.
| | h2. Situation |
| | Set up a configuration to generate builds of a project and achieve below purposes: |
| | # QuickBuild should use next unreleased version of that project in JIRA as version of the new build. |
| | # For JIRA issues marked as fixed in SCM commit comments, QuickBuild should update status of these issues in JIRA to be _resolved_ under the developer's JIRA account. |
| | # QuickBuild should mark corresponding versions of the project in JIRA as _released_. |
| | # For all above resolved issues, QuickBuild should update the _fix version/s_ field to include the build version. |
| | # When navigate to build detail, issue keys in the commit comments should be rendered as issue links. |
| | # User should be able to view all resolved/related issues in a particular build. |
| | # User should be able to view all builds and SCM changes relating to a particular issue at JIRA side. |
| | |
| | h2. Demonstration |
| | # Switch to [versions screen|http://jira.demo.pmease.com/browse/TST#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel] of the demo JIRA instance. The next unreleased version is the same as next build version displayed at [QuickBuild side|http://demo.pmease.com/dashboard/90]. You will also find that all built versions at QuickBuild side are marked as released here. |
| | # Switch to [scm changes page of latest build of the demo project|http://demo.pmease.com/build/90:latest]. All issue keys in the commit message are hyper-linked to JIRA. |
| | # Switch to [issues page of latest build of the demo project|http://demo.pmease.com/build/90:latest/scm_changes]. All issues corresponding to current build are listed there, and QuickBuild has resolved all issues under the name of "robin" at JIRA side based on "fix" keywords found in robin's commit message. |
| | # Click any issue key in the issues page to get navigated to issue detail page in JIRA, and you will find that the issue's _fix version/s_ field is updated to include current build version. |
| | # In the issue detail page opened above, you will find two additional tabs, respectively _QB Builds_, and _QB Changes_. The _QB Builds_ tab displays all builds relating to this issue, while _QB Changes_ tab displays all SCM changes relating to the issue. You may also be able to view/diff changed files in _QB Changes_ tab. |
| | |
| | h2. Resolution |
| | To get QuickBuild displaying JIRA issues: |
| | # Configure JIRA to accept remote API calls. Remote API call option can be turned on/off by logging in as JIRA administrator, switching to _Administration_ tab, clicking _General Configuration_ link at left side of the screen, and clicking the _edit configuration_ link. |
| | # Set up JIRA server information at QuickBuild side by switching to the [JIRA server setting page|http://demo.pmease.com/settings/90/jira_server]. |
| | |
| | To configure QuickBuild to pick up next unreleased JIRA version as next build version, switch to [general setting page|http://demo.pmease.com/settings/90/general] and specify next build version as _Use first unreleased version of associated JIRA project_. |
| | |
| | To configure QuickBuild to auto-update status of JIRA issues based on issue actions in SCM commit messages, you will need to add the _Update JIRA Issues_ step as shown in [steps page of the demo project|http://demo.pmease.com/settings/90/steps]. QuickBuild tries to update issues using developer's own JIRA account, and this required that: |
| | # The user name in SCM system can be mapped to a QuickBuild user. Taking the demo project for example, the user "robin" is mapped to QuickBuild user "robinshine" in [repository definition|http://demo.pmease.com/settings/90/repositories]. This requirement will be automatically met if your SCM system and QuickBuild have been configured to authenticate against the same LDAP system. Refer to the [LDAP authentication] for details. |
| | # If user name/password of the mapped QuickBuild user is not the same as in JIRA, you will need to specify JIRA account by editing my setting page of the QuickBuild user. This requirement will be automatically met if QuickBuild and JIRA have been configured to authenticate against the same LDAP system. Refer to the [LDAP authentication] for details. |
| | |
| | To configure QuickBuild to auto-release corresponding JIRA versions and update _fix version/s_ field of relevant issues, you will need to add the _Release JIRA Version_ step as shown in [steps page of the demo project|http://demo.pmease.com/settings/90/steps]. Also please make sure that the JIRA account specified at [JIRA server setting page|http://demo.pmease.com/settings/90/jira_server] has below permissions: |
| | # Be able to release existing versions and create new versions in relevant projects in JIRA. |
| | # Be able to update issues of corresponding projects. |
| | |
| | To configure JIRA to display _QB Builds_ tab and _QB Changes_ tab, do the following: |
| | | # Install the QuickBuild plugin for JIRA following instructions in [this page|Integrating QuickBuild with JIRA]. |
| | | # Install the QuickBuild plugin for JIRA following instructions in [this page|Integrating JIRA with QuickBuild]. |
| | # Start up JIRA, login as JIRA administrator, switch to Administration tab, and click the _QuickBuild Server_ link at left side of the screen. In the QuickBuild servers page, we've specified below setting for this demo: |
| | ## Server Name: Demo QuickBuild Server |
| | ## Host URL: http://demo.pmease.com |
| | ## User name/password: specify the QuickBuild account with permission to access build changes |
| | ## Associated Projects: TST=Demo/Build Setup Tutorials/JIRA Integration |
JIRA Integration