Atlassian Integration Guide : After Dragons This page last changed on Dec 07, 2009 by smaddox.
| Is there life after Dragons? Now that you have successfully set up your Atlassian integrated suite, we have some useful information about what you may want to do next. There's no rush. Get to know the applications and show off your T-shirt for a while first. Then choose any of the points below that may be relevant to you.
On this page: Using the Free IDE Connectors Atlassian Connector for Eclipse Atlassian Connector for IntelliJ IDEA Adding More Atlassian Tools to your Suite Crucible for Code Review Clover for Code Coverage Hints after Initial Setup Adding Users to your Atlassian Integrated Suite Running Bamboo in a Console Window ## Using the Free IDE Connectors This information is useful to developers who use Eclipse or IntelliJ IDEA. You can work with JIRA issues, Bamboo builds and FishEye links directly within your IDE (integrated development environment), using the Atlassian IDE Connectors. The connectors are free. #### Atlassian Connector for Eclipse
Installation | You can install the connector directly from the Eclipse software updates manager, or via the Mylyn Connector Discovery wizard, or from a zipped archive. Full instructions are in our installation guide. Here are the instructions for Eclipse 3.5 using the Mylyn Connector Discovery wizard: Ensure that you have already installed Mylyn 3.2.x. (If you are using an Eclipse package from the Eclipse download site, Mylyn 3.2 is already included in any package except the Classic download.) In Eclipse Mylyn, open the 'Task Repositories' view. (In Eclipse, click 'Windows', 'Show View', 'Other' and select the 'Task Repositories' view from the 'Tasks' category.) Click the 'Add Task Repository' icon. The 'Add Task Repository' screen appears. Click the 'Install More Connectors' button. The 'Mylyn Connector Discovery' screen appears. Select the Atlassian Connector and click 'Finish' to install it.
Overview | Working with Bamboo builds in Eclipse, you can: View a list of the builds you are monitoring, in the Bamboo view in Eclipse. Receive notification of failed builds and other build changes. Open the Bamboo build details in an Eclipse editor. Open the Bamboo build details in your web browser, displaying the Bamboo web interface. Run a build on the Bamboo server. View a Bamboo build log. View test results. View changed files in the build. Comment on a Bamboo build. Label a Bamboo build. Add a new task based on a failed build. Working with FishEye in Eclipse, you can open a file from Eclipse in FishEye and send your colleagues a FishEye link to your file. Working with JIRA issues in Eclipse: For information on setting up your JIRA server in Eclipse, please read the configuration guide. Please refer to the JIRA Mylyn documentation for user guidelines.
Videos and tours | See our website.
#### Atlassian Connector for IntelliJ IDEA
Installation | You can install the connector from the 'Plugins' menu in IntelliJ IDEA, as described in our installation guide. Here are the instructions in brief: Open the IDEA plugin manager. (Go to IDEA's 'File' menu and select 'Settings', 'IDE Settings', 'Plugins'.) Right-click 'Atlassian Connector for IntelliJ IDEA' in the 'Available' plugins tab. Select 'Download and Install'.
Overview | Working with Bamboo builds in IDEA, you can: Receive notifications of failed builds. View the builds. Re-run a build. Open the Bamboo build details in an IDEA output tool window. View the build history for a selected plan. View a Bamboo build log. View failed tests and stack traces. Click a link in a stack trace to go directly to the code that failed. Re-run a failed test. View changed files. Compare the build version of a file with your local version. Compare the build version of a file with the previous repository version. Open the repository version of a file in your IDEA editor. Comment on a Bamboo build. Label a Bamboo build. Working with FishEye in IDEA, you can open a file from Eclipse in FishEye and send your colleagues a FishEye link to your file. Working with JIRA issues in IDEA, you can: View a filtered list of issues. Make a JIRA issue your active issue. Create a new JIRA issue. Comment on a JIRA issue and view existing comments. Create a changelist from a JIRA issue. Log work on a JIRA issue. View a JIRA issue in an IDEA output tool window. View stack traces from a JIRA issue and click through to the relevant source file. View and download attachments on an issue. Assign an issue to yourself or another user. Perform workflow actions on a selected issue. Use the issue quick access options to open an issue in IDEA.
Videos and tours | See our website.
## Adding More Atlassian Tools to your Suite This section tells you about more Atlassian developer tools that you can add to your integrated suite: Crucible for code review and Clover for code coverage. #### Crucible for Code Review Crucible is a web application that integrates with your source repository, providing workflow and database storage for your code reviews. With Crucible, you can collaborate on code reviews across time zones and geographical locations.
Installation | Crucible is part of the FishEye installation. Since you have already installed FishEye, it is very simple to enable Crucible. Just add your license key and give Charlie permission to use Crucible: Go to your FishEye URL in your web browser, e.g. `http://localhost:8060/`. Click 'Administration' at the bottom of the FishEye screen, to open the FishEye Admin screens. Enter your FishEye administration password, if prompted. This is the password you chose when setting up FishEye in Dragons stage 5. Click 'Sys Info/Support' in the left-hand panel. Scroll down to the bottom and click 'Edit License'. Enter your Crucible license key into the 'Crucible License Key' field. If you do not already have a Crucible license, you can obtain a free evaluation license. Click 'Update'. The logo and heading at top left of your screen will now include the Crucible branding. Click 'Users' in the left-hand panel. The 'User browser' will appear. Note that there is an asterisk '*' next to username 'charlie', meaning that Charlie does not have permission to use Crucible. Click 'Edit' next to Charlie's name. The 'User Details' screen will appear. Select the 'Active Crucible user' checkbox. Click 'Apply'.
Overview | Now that you have enabled Crucible, you can start reviewing the code committed to your repository: Click the FishEye+Crucible logo at top left to go to the dashboard. Make sure you have the 'All Activity' tab open on the dashboard and can see the two commits. Click the downward-pointing arrow next to the cog icon at the right-hand side of the screen next to 'committed 2 to Dragons'. A drop-down menu will appear. Select 'Create Review'. The 'Edit Review CR-1' screen will appear. Now you need some people to review the code: If you have already added more users to Crowd, you can select them as reviewers. Start typing a name into the 'Reviewers text box. Crucible will offer a list of matching names for you to select from. If you have already set up a mail server in FishEye, you can enter an email address in the 'Invite Reviewers' text box and click 'Invite'. The person will receive an email message inviting them to join the review. They will need a Crowd username before they can start. Otherwise, for the purposes of this exercise, you can continue with no reviewers. Leave the other fields at their default values and click 'Start Review'. If you see a warning that the review has no reviewers, click 'Confirm'. The review details appear for your new Crucibe review 'CR-1'. Please refer to the Crucible documentation on: Performing a review that has been assigned to you. Adding files and changesets to the review. Managing the review workflow. Integrating your reviews with JIRA. Screenshot 1 (click to enlarge): A Crucible review
Screenshots and tours | There are many different ways to use Crucible. See the documentation and the website for inspiration.
In your IDE | Try the awesome Atlassian IDE Connectors to conduct Crucible code reviews directly within Eclipse or IntelliJ IDEA. With the connector, you can perform pre-commit reviews as well as post-commit and patch reviews. The Atlassian IDE Connectors are free.
#### Clover for Code Coverage Clover is a code coverage tool for Java. 'Code coverage' means that Clover measures how much of your Java code is executed by your tests. Clover has several differentiating features, including the ability to optimise your test execution (make your builds faster), measure per-test coverage and produce interactive HTML reports. Clover provides plugins for Eclipse and IntelliJ IDEA.
Installation | Clover offers several different installation options, depending on your development and build tools. The details are in the Clover documentation. Below are the instructions for using Clover within Bamboo. (This configuration will work only for Java projects using Maven 2 or Ant.) Since you have already installed Bamboo, it is very simple to enable the Clover plugin for Bamboo. All you need is a license key: Go to your Bamboo URL in your browser, e.g. `http://www.foobar.com:8085`. Log in to Bamboo with username `charlie`. Make sure you are on the 'All Plans' tab of the 'Home' screen. (Click 'Home' in the top navigation bar, then click 'All Plans'.) Click the name of the plan, 'Main', to open the plan summary. Click the 'Configuration' tab. Click the 'Builder' tab. Click the 'Edit Plan' link. Select the checkbox labelled 'Use Clover to collect Code Coverage for this build'. A new section of the screen will open. Select the radio button labelled 'Automatically integrate Clover into this build'. More reporting options appear. At this stage it is fine to leave them unselected. Optional – Enter your 'Clover License': If you have a Clover license, enter the license key. If you do not have a Clover license, leave the license field empty. You can use Clover in Bamboo for 30 days without obtaining a license. Click 'Save'.
Overview | Now that you have Clover in Bamboo, you can run a build and see the code coverage. You can also use Bamboo's report generator to see the Clover Lines of Code report and the Clover Code Coverage report. If you would like to try it out with our sample repository, follow the instructions below. Please note: Running the build of our sample project will take quite a long time: approximately 20 minutes. This is because the build procedure will download and start the Confluence web application so that it can run the integration tests. Click 'Build Actions' near the top right of the Bamboo build plan screen, for your Dragons Main plan. A dropdown menu will appear. Click 'Run Build'. The build will start. If this is the second time you have run a build, it will be called DRAG-MAIN-2. Have a cup of hot chocolate while the build runs. It will take some time – approximately 20 minutes. Here is a summary of what it will do: Download the Clover plugin for Bamboo. Run the unit tests. Download the Confluence web application. It does this because our sample project is a Confluence plugin. Start a Confluence server in Tomcat on port 1990. Run the integration tests. Shut down Confluence. Collect the Clover artifacts. Finally, report that the build is successful. (Or that it has failed.) When the build has finished, click the build name, e.g. DRAG-MAIN-2, near the top right of the screen. The 'Build Result' screen will appear. Click the 'Clover' tab. The 'Clover Code Coverage' screen will appear. Screenshot 2 (click to enlarge): Clover in Bamboo
Classic Clover | More things you can do with Clover: From within IntelliJ IDEA, view recently-run tests via the Test Run Explorer, see the Java code annotated with coverage information, view coverage cloud and treemap reports, and optimise your test builds. From within Eclipse, view recently-run tests via the Test Run Explorer, see the Java code annotated with coverage information, view coverage cloud and treemap reports, see the unit tests and methods that generated coverage for the currently opensource file, and optimise your test builds. Use Clover for Ant, interactively or in automated builds, with a range of current and historical reports, clouds and charts. Use Clover for Maven 1 or for Maven 2, view a range of historical and custom reports, and optimise your test builds.
Videos and tours | See our website.
## Hints after Initial Setup These hints may be useful in the early days after you complete your initial setup. Click the links to see the details of each hint. #### Adding Users to your Atlassian Integrated Suite During the Atlassian Dragon quest, you added just one user to your integrated suite: Charlie of Atlassian. Very soon you will want to add more users, and in particular users who are not administrators. We recommend that you use Crowd for all user and group management. Below is a suggested plan of action and a hint about what to do if new users experience a delay before they can see their JIRA projects. #### Running Bamboo in a Console Window If you experience problems with running Bamboo as a Windows service you can start Bamboo in a console window instead, by running {`BAMBOO_INSTALL}\bin\BambooConsole.bat`. ##### RELATED TOPICS Here Be Dragons Attachments: FishEyeCogIcon.png (image/png) CrucibleReview.png (image/png) CloverInBamboo.png (image/png)

Document generated by Confluence on Apr 07, 2010 22:35