A Swarm project is made up of a group of Helix Server users who are working together on one or more codelines within the Helix Server. A project's definition includes one or more branches(noun) A set of related files that exist at a specific location in the Perforce depot as a result of being copied to that location, as opposed to being added to that location. A group of related files is often referred to as a codeline. (verb) To create a codeline by copying another codeline with the 'p4 integrate', 'p4 copy', or 'p4 populate' command. of code, and optionally a jobA user-defined unit of work tracked by Helix Server. The job template determines what information is tracked. The template can be modified by the Helix Server system administrator. A job describes work to be done, such as a bug fix. Associating a job with a changelist records which changes fixed the bug. filter, automated test integration, and automated deployment. This section provides an introduction to the interactions users have with projects. See the Projects chapter for details on managing projects.
Projects are listed on the Swarm home page below the project dropdown menu. The first time you log-in to Swarm you will see a list of the projects you own or are a member of. Logged-in users can choose to display all projects or just the projects they are an owner or member of by clicking on the dropdown above the projects list:
View a project by doing one of the following:
https://myswarm.url/projects/project-name
The project Overview tab shows a description of the project.
The project's Overview tab is only displayed if there is a README.md
in the project's mainline.
The README.md
file can contain Markdown text, allowing a formatted description of the project to be provided. See Markdown in projects for a description of the type of formatting that is supported. See Mainline branch identification for details on how to configure the mainline of a project.
The following information is displayed in the project sidebar:
The project Activity tab shows the activity stream for the project
The following information is displayed in the project sidebar:
The project Reviews tab shows a list of code reviews specific to the project.
For more details on browsing, filtering, and searching reviews, see Reviews list.
The project Files tab shows a list of files for the project, starting with a folder view representing each branch. Branches are designated with the branch icon .
The project's main branch, identified by using a name such as main, mainline, master, trunk, is sorted to the top of the list of branches and appears in bold. The list of names can be configured, see Mainline branch identification for details.
For more information on browsing files, see Files.
The project Commits tab shows a list of changes made to the project.
For more details on history browsing, see Commits.
The project Jobs tab shows a list of jobs associated with the project.
The Jobs tab is only displayed when the project configuration includes a job filter. See Add a project for details.
For more details on browsing and searching jobs, see Jobs.
Private projects, introduced in Swarm 2016.2, provide a way to make specific projects and their activity less visible to Swarm users. When a project is made private, only the projects owners, moderators, and members, plus users with super privileges in the Helix Server, can see the project, its activity streams, and ongoing reviews.
If you are logged in as an owner, moderator, or member of a private Swarm project, that project appears on the Swarm home page with an eye icon to indicate that it is private and has limited visibility:
Similarly, the eye icon appears beside the project's title when viewing the project. When you hover your mouse over the eye icon, a tooltip appears indicating that this project is indeed private.
The following are important caveats regarding private projects: