Add a project

  1. The Add Project button On the Swarm home page, click the + icon at the top-right of the projects sidebar.

    Note

    The ability to add projects can be limited to administrators only. When limited, the + icon does not appear at the top-right of the projects sidebar for non-administrators.

    The Add Project page appears:

    The Add Project page

  2. Provide a name for the project.

  3. Optionally provide a description.

  4. Optionally click the Only Owners and Administrators can edit the project checkbox. When checked, a field is displayed allowing you to add a new owner. The field auto-suggests users within the Perforce service as you type.

    The Add Owner field

    Once specified, modifying the project's definition is restricted to project owners and administrators (users with admin-level or super-level privileges in the Perforce service).

  5. Specify at least one team member. This field auto-suggests users within the Perforce service as you type.

  6. The Add Branch link Optionally click the Add Branch link to display the branch drop-down dialog:

    The branch drop-down dialog

    1. Enter a short Name for the branch.

    2. Enter one or more branch paths, one per line.

      Note

      Each branch path should be expressed in depot syntax. Wildcards should not be used; the only exception is that the branch path can end with the Perforce wildcard ...

      For more information, see Command Reference: File Specifications.

    3. Optionally check the Only Moderators can approve or reject reviews checkbox. When checked, a field is displayed allowng you to add a new moderator. The field auto-suggests users within the Perforce service as you type.

      The Add Moderator field

      Once the branch specification is complete and the project has been saved, changing the state of any review associated with this moderated branch is restricted as follows:

      • Only moderators can approve or reject the review. Moderators can also transition a review to any other state.

      • The review's author can change the review's state to Needs Review, Needs Revision, Archived, and can attach committed changelists. Normally, the review's author cannot change the review's state to Approved or Rejected on moderated branches. There is one exception: if the author is the only moderator on the branch, they may approve or reject their own review.

      • Project members can change the review's state to Needs Review or Needs Revision, and can attach committed changelists. Project memebers cannot change the review's state to Approved, Rejected, or Archived.

      • Users that are not project members, moderators, or the review's author cannot transition the review's state.

      • For the review's author and project members, if a review is not in one of their permitted states, for example if the review's state is Rejected, they cannot transition the review to another state.

        These restrictions have no effect on who can start a review.

    4. The Done button Click the Done button to accept your branch specification.

    Once the branch definition has completed, if any moderators were specified, the number of moderators for that branch is displayed in the list of branches:

    Branch moderators count.

  7. Optionally specify a job filter. The job filter allows you to specify criteria that are used to associate jobs with projects. For example, entering Subsystem=ProjectA associates jobs whose subsystem field is set to ProjectA with the current project.

    Note

    This job filter is simpler than the filters available in other Perforce clients. The filter must be expressed as field=value pairs; bare keywords are not permitted. The asterisk for wildcard matching is permitted, but no other filter expression syntax is permitted.

  8. The checkbox indicating automated test activation status Optionally click the Enable checkbox beside Automated Tests to display the automated tests configuration fields.

    The Automated Tests drop-down dialog Specify a URL that triggers a test execution. Use the special arguments described in the dialog to help compose a URL that informs your test suite with important details. For more details, see “How can I integrate my test suite to inform review acceptance or rejection?”.

  9. The checkbox indicating automated deployment activation status Optionally click the Enable checkbox beside Automated Deployment to display the automated deployment configuration fields:

    The Automated Deployment drop-down dialog Specify a URL that triggers a deployment of the project's code. Use the special arguments described in the dialog to help compose a URL that informs your deployment program with important details. For more details, see “How can I automatically deploy code within a review?”.

  10. Save button for Project configuration Click Save.

    Note

    The Save button is disabled if any required fields are empty.