Need help with other JFrog products?
Good news! Enterprise-scale distribution is now handled through the robust JFrog Platform.
Please contact us with any questions.
In the Owned Repositories work area of the homepage, click the New Repository button. The Create New Repository page is displayed.
Enter the details of the repository (repository metadata) and click the Create button
An empty repository, owned by the organization of which you are a member, is created, and the Repository page is displayed.
Note: There are other ways to create a new repository within Bintray. For example, there is a New Repository button in the Owned Repositories work area of your user profile and also in the Repositories form of the Edit Your Profile page when editing your profile. If you are a member of an organization (and have the proper authorization), you can also create a new repository from the Organization Profile page. A repository created from within an organization is owned by the organization (in all cases you own the repository that you create).
Editing a Repository
The details of an existing repository can be edited when necessary. This can only be done by the repository owner (or, if the repo is within an organization, by any member with the proper authorization).
Note that editing a repo means editing metadata that can be modified - some metadata cannot be changed); it does not mean editing the data within the repository. To perform actions on repository contents you can add packages, link packages, add versions and upload files manually or using tools).
There are four tabs which enable you to edit a repository:
To edit the repository details, access the repository’s page and click the Edit button under its name:
In the General Settings page, you can change the avatar, add or edit a description, and add or edit tags (these are the metadata fields that you can still change after creating a repository).
Click Update when done.
Note that this is where you can assign the repository to a business unit so you can monitor usage of all your repositories by business unit.
Through the Permissions tab, you can define the access privileges that different teams in your organizations have to content in your repository. For more details, please refer to Teams and Permissions.
If you have Enterprise level Bintray account, you can also restrict the countries from which end users can download content from your repository by specifying either a whitelist or a blacklist, from the Geo Restriction tab. A whitelist specifies the countries from which your repository can be accessed while a blacklist specifies the countries from which access is blocked.
TIP - Use the filter at the top of the countries list to help you find the countries for your whitelist or blacklist
If you have an Enterprise level Bintray account, you can restrict IP addresses from which end users can download content from your repository by specifying a whitelist and/or a blacklist of CIDRs per repository. You can do this from the IP Restriction tab. A whitelist specifies the IPs from which your repository can be accessed while a blacklist specifies the IPs from which access is blocked.
If the CIDRs you specify overlap (some IP addresses are included in both the whitelist AND the blacklist), then the blacklist will take precedence and those IP addresses will be blocked. If you specify the exact same CIDR in both the whitelist and the blacklist, Bintray will reject this and an error message will pop up.
The metadata fields that define a repository are as follows (they are all in the General Settings form):
Avatar: The avatar assigned to the repository may be uploaded by the user (as an image file) at any time. If no avatar is uploaded, a generic one is automatically assigned.
Visibility: Specifies whether the repository is Private (which means the right privileges are required to access the repository), or public (which means anyone can access the repository to download files)
Name: Entered by the user when they create the repository. This field cannot be changed.
Type: Entered by user when the repository is created. This field cannot be changed. The repository type associates it with a specific build tool or package management tool (Maven, Debian, RPM, etc.); a repository may also be generic, not associated with any specific build or management tool.
Business Unit: Specifies the Business Unit to which this repository belongs (Only available for repositories created in an Enterprise organization).
Description: Optional free text that a user can add, informing others about the details of their repository. This text can be changed at any time.
Tags: Text tags are keywords and/or terms assigned to the repository according to topic or theme and are designed to help other users find it. Tags are optional and can be changed at any time.
When displayed in Bintray, additional information about a repository is displayed such as the number of packages. This shows what Bintray entities are stored in the repository, such as packages and versions, and information
about Bintray interactions, such as the owner’s name.