Distribute a Release Bundle (v2) using the Platform UI

JFrog Artifactory Documentation
Products
JFrog Artifactory
Content Type
User Guide
ft:sourceType
Paligo

Release Bundle v2 versions are distributed from the version timeline.

Subscription Information

This feature is supported with the Enterprise+ license.

To distribute a Release Bundle v2:

  1. In the Application module, select Artifactory > Release Lifecycle. The Release Lifecycle dashboard is displayed.

    Note

    Distributing Release Bundles v2 using the dashboard requires Distribution 2.22.1 or above.

  2. Click the name of the relevant Release Bundle to open the kanban board.

  3. Click the kanban card for the relevant Release Bundle version to open its timeline.

  4. Find the Release Bundle version you wish to distribute and from the Actions menu, select Distribute. The Distribute window is displayed.

    Dashboard_Actions-menu_distribute.png

  5. In the Distribution Targets tab, select the desired distribution targets (e.g. Edge nodes).

    first_or_second_distribte_-_selecting_edges.png

    Note

    A checkmark next to the distribution target indicates that the selected Release Bundle version has already been distributed to that target. Nevertheless, it is possible to distribute the same version again to that target.

    RBv2-version-already-distributed-to-target.png

    Tip

    If no distribution targets are displayed, click the link provided in the window to see suggestions about the possible cause.Distribution Target Troubleshooting

  6. (optional) Select the Auto create missing repositories checkbox to have any missing repositories in the distribution targets created automatically. If this option is not selected and a missing repository is detected, distribution will fail.

  7. Click Next to move to the Additional Settings tab.

  8. (optional) Specify a list of input and output regex mapping pairs that define where the queried artifact is located and where it should be placed. Use this option if the path on the target is different than the source path.

    Important

    Path mapping can be performed only during the first distribution or export of a particular Release Bundle version. The following message is displayed during subsequent operations.

    path-mapping-already-defined.png
    first_distribute_before_adding_the_path_mapping.png

    There are 3 options for defining path mappings:

    1. You can define custom mapping pairs manually and click Add.

    2. You can click Use Template to use one of the provided Path Mapping templates:

      Template

      Description

      Change Repository

      All files in a specific repository on the source Artifactory service are mapped to a different repository on the target.

      Change Folder

      All files are moved to a specific folder in the target.

      Rename Folder

      All files in a specific folder on the source Artifactory service are mapped to a different folder on the target.

    3. If the Default Path Mapping by Last Promotion feature is enabled (requires Distribution 2.26.1 or higher), the repositories used for the most recent promotion of this Release Bundle version are provided as the default path mapping. If you do not want this path mapping definition, click the X to remove it.

      default-path-mapping_distribute.png

  9. Click Distribute. The status of the distribution operation is displayed in the version timeline. There will be an entry in the timeline for each distribution target. For example, if you distribute the Release Bundle to 3 Edge nodes, three entries will be added to the timeline (one for each target).

    In addition, a new card will appear on the distribution board beneath each distribution target.

    Warning

    When JFrog Xray is used to scan Release Bundles for potential vulnerabilities and license violations, Xray will block promotion if the Release Bundle violates a Policy that has a blocking action defined. Scan results are shown in the timeline event, as shown below.