Asset Management

Asset Management

Pulling an object

Pulling an object

Use the pull action to update the organization with objects in the source control repository. You can pull a single asset, a project, or a folder. When you pull a project or folder, you can exclude any assets in the project or folder that you don't want to include in the pull.
  1. To pull a project from the global repository, click
    Pull from Global Git
    . Select the project that contains the objects you want to pull and click
    Next
    .
  2. To pull a project from a repository or branch that's configured at the project level, on the
    Explore
    page, select the asset or folder. Click
    Actions
    and select
    Pull
    .
    You can't pull more than one project at a time.
  3. To pull a single asset or folder, on the
    Explore
    page, select the asset or folder. Click
    Actions
    and select
    Pull
    .
  4. Select the Git hash that you want to pull and click
    Next
    .
  5. Review the list of assets. You can clear the check box for any of the assets that you don't want to include in the pull. By default, all of the assets are selected.
  6. Review the actions in the
    Status
    column for each asset. These actions will occur when the pull action is performed.
  7. If an asset requires a connection, select a target connection to use in the organization or accept the default.
    You can't create a new connection during the pull process.
  8. If an asset requires a runtime environment, select a target runtime environment to use in the organization or accept the default.
    You can't create a new runtime environment during the pull process.
  9. To publish assets after you pull them, select
    Publish Application Integration assets after pull
    and
    Publish Taskflow(s) after pull
    as required.
  10. Optionally, click
    Test
    to see if errors might occur as a result of the pull action.
  11. Click
    Pull
    .
    The pull action generates a log showing details of this action. You can view the log on the
    Source Control Logs
    page in Monitor.

0 COMMENTS

We’d like to hear from you!