Need help with other JFrog products?
Have a question? Want to report an issue? Contact JFrog support
Creating a New Repository
Once your'e logged in to Bintay, you can create respositories in your personal organization or in any organization in which you have Admin permissions.
In the Owned Repositories section, click Add New Repository. The Add Repository page is displayed.
Enter the details of the repository (repository metadata) and click Save.
An empty repository, owned by the organization of which you are a member, is created, and the Repository page is displayed.
There are different methods for creating a new repository within Bintray. For example, there is a New Repository button in the Owned Repositories section 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).
Viewing Repository Settings
The details of an existing repository can be edited when necessary. This can only be done by the repository owner or by other members of the organization who have admin permissions.
Note that editing a repository results in editing the metadata and does not make changes to the data within the repository. Actions on contents include adding packages, linking packages, adding versions and uploading files either manually or via external tools.
The metadata fields configurable in the Edit Repository page define a repository as follows:
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.
Name: Entered by the user when they create the repository. This field cannot be changed.
Repository Type: Entered by the 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.
- Public repository/ Private repository: 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)
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.
Managing a Repository
The Repository page contains three tabs - Packages, Permissions and Restrictions.
Admin Permissions are Required
The three tabs are displayed in the Repository page to users with admin permissions.
Lists the packages located in the repository and allows you to add packages to your repository.
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.
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 Restrictions tab. A whitelist specifies the countries from which your repository can be accessed while a blacklist specifies the countries from which access is blocked.
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.
Content Update Restrictions
Applying the Content Update Restrictions feature provides a prevents any changes to be made to the package version after the predefined period. This is useful for preventing any updates made to older version, as the Admin can configure the content update restriction allowing publishers to update a version but lock it after the allowed update period.
The Content Update Restriction feature is available to Bintray Pro and Enterprise users.