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.
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
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.
This section tells you about another Atlassian developer tool that you can add to your integrated suite, Clover for code coverage.
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.
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:
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
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.
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. You also configured all the Atlassian applications to centralise their user management in JIRA. We recommend that you use JIRA for all user and group management.