Manage Project Resources

Project Wiki (Confluence)

Wiki space is managed using the Atlassian Confluence tool. This is why a Confluence account is created upon signup with MuleForge.

Edit Your Project's Homepage

1. Go to your project's homepage.
2. Log into Confluence by clicking 'View' in the top navigation bar, 'Account' and 'Log in'.
3. Click 'Edit' from the top navigation bar, 'Edit this page...'
4. This loads a simple text editor from where you can edit the contents of your homepage.
5. Remove the default text 'Despot To Do: Add Documentation here' and write your own documentation in its place.
6. Click 'Save'.

Project Source Control (Subversion)

Despots ultimately control who can commit source to the project. New Project Developers approved by the Despot have Subversion commit rights in the project.

Project Build Plan (Bamboo)

MuleForge projects are configured to be automatically built using Bamboo, a Continuous Integration Build Server from Atlassian. The source code build frequency is set to 30 minutes; while the snapshot build frequency is set to 1 day. If you would like these settings to be changed, please email support@muleforge.org requesting new build frequency settings.

Note that Maven2 (M2) is the standard build tool for MuleForge projects.

Project Details within the MuleForge Project Catalogue (MFPC)

As described in the MuleForge Hosting Environment, each project is listed as an issue within the MuleForge Project Catalogue (MFPC) JIRA project. The issue within MFPC holds the details of the project. As a despot, you need to update the info from time to time. Mainly, the fields that would required an update include the Project Maturity, Supported Java Versions and Download URL fields.

To access the project details in MFPC:

• Go to the homepage of the project.
• Click 'Project Properties' under the 'Administration' heading from the left navigation bar.

To update the project details:

• Currently, the only way to do this is to email support@muleforge.org with a request to update the desired fields of your project.

Note on the Project Maturity Field

• Read the Project Maturity documentation to learn about the various Project Maturity settings.
• If the 'Project Maturity' level is '4 - Beta' or '5 - Production', the Download URL must be set to point to your Snapshot Distribution Repository. (See Understanding MuleForge M2 Repositories and Downloads.) This will cause a Download button to be available in the MuleForge Project Search page.

  Only request the 'Project Maturity' level to be set to '4 - Beta' or '5 - Production', after you produce a release for your project.

Project Issue Tracker (JIRA)

Access the JIRA associated with your Project

1. Go to your project's homepage.
2. From the left navigation bar, click 'JIRA Tracker' under the 'Project Info' heading.
3. Log into JIRA, by clicking the 'Log In' link at the top right of the page and entering your JIRA credentials.

A despot is required to administer the project's JIRA System. Administering a project includes tracking bug and improvement issues, creating components and project versions as well as a defining a RoadMap for the development of the project. Some notes are detailed below. Full documentation about project management using JIRA is found at the Atlassian JIRA Website.

Track JIRA Issues

1. Log in, unless already logged into JIRA.
2. If not already within the JIRA page of your project, click on 'Browse Projects' in the top navigation panel and select your project from the list.
3. By default, the 'Open Issues' tab is displayed.
4. Here you can view all the open issues in each component and the open issues due to be fixed per version.

Create, Edit, Delete a Component

It is generally advisable to create components in order to be able to categorise issues.

To create a component:

1. Log in, unless already logged into JIRA.
2. If not already within the JIRA page of your project, click on 'Browse Projects' in the top navigation panel and select your project from the list.
3. Click the 'Administer Project' link.
4. Within the 'Components' section, click 'Add' to add a new component.

When a component is added, a link to it will be placed on the JIRA page of your project. Issues may be created within the new component.

To edit or delete a component, click on the component itself and find the following two links: 'Edit Component' and 'Delete Component'.

Manage Project Versions

JIRA also offers the possibility to manage versions of your project.

1. Log in, unless already logged into JIRA.
2. If not already within the JIRA page of your project, click 'Browse Projects' in the top navigation panel and select your project from the list.
3. Click 'Administer Project'.
4. Within the 'Versions' section, click 'Manage' to be able to manage versions.

Having issues organised into components associated with different versions of your project makes it easier to track issues.