With TeamForge-Nexus integration enabled, each project can have one or more binary
repositories.
Remember:
Before you can create a repository for binary artifacts, a site administrator
must set up TeamForge-Nexus integration and add one or more binary servers to
your TeamForge site.
-
Click Binaries in the project navigation bar.
-
Click Create Repository.
-
Type or select the values for the following fields in the Create
Repository page.
Tip: Hover your mouse over the Help icon (question mark icon) for
relevant tooltip.
- Repository Name and Repository
ID: Type a name and ID for the binary repository.
- Server: Select a binary repository server from
the servers available in the drop-down list.
- Repository Type: Select one of the following
types from the drop-down list: Hosted Repository or
Proxy Repository or Virtual
Repository.
- Provider: Select the content provider of the
repository from the drop-down list.
- Repository Policy: Repositories can store
artifacts of a release or snapshot or both. Select a policy from the
drop-down list.
- Override Local Storage Location: Leave this blank
to use the default local storage location. To change the local storage
location, type the path (URL) in the following format.
- Windows: file:/{drive-letter}:/
- Other operating systems:
file://
-
Modify the default access settings such as Deployment
Policy, Allow File Browsing,
Include in Search and Publish
URL, if required.
-
Modify the Not Found Cache TTL duration (in minutes), if
required.
-
Click Save.
The binary repository is created.
After creating a binary repository, you can now configure the runtime (TeamForge
Orchestrate) so that your Nexus runtime events are published to Orchestrate. See
Configure runtime for binary artifact repositories.