Fetch from Git

Use the Fetch from Git bundled plugin to download source files from a Git repository.

Note: To fetch content from your current product or Git repository, PulseUno uses the Fetch Sources step.

To configure the Fetch from Git step:

  1. Add the Fetch from Git step to a chain, as described in Create chains.

  2. Enter the plugin configuration details:

    Field Description
    Title Enter a name for the plugin step.
    URL for repository

    Enter the network address of the Git repository to fetch from, for example:

    https://github.com/jenkinsci/dimensionscm-plugin.git
    git@git.server.com:author/project.git

    Clone depth

    Available from 25.2:

    Specify the number of revisions or commits.
    Branch (Optional) Specify a branch to fetch.
    Commit ID or a tag (Optional) Specify a commit or tag to fetch. By default, the plugin fetches the last commit.
    Paths to fetch (Optional) To fetch only specific directories, enter directory paths, one path per line. By default, the plugin fetches the entire branch.
    Clean workspace before fetching (Optional) Select this option to clean your local workspace before fetching source files.
    Workspace subdirectory to fetch files into

    (Optional) Specify the subdirectory to download source files to, for example:

    /subrepository

    By default, the fetched files replace the entire content of the local workspace.
    Authentication type

    Select how to connect to the Git repository from which you're fetching files:

    • Automatically using PulseUno
    • Anonymously
    • By login and password
    • By private key
    Control options

    (Optional) Define the control options for the plugin step:

    • Enable step. By default, the step is enabled to run. Clear this option if you need to deactivate the step.

      Deactivated steps are skipped when the chain runs.

    • Fail the step. Specify the conditions for failing the step, such as unit test failures, findings criteria, and/or console log entries.

    • Mark step as unstable. Specify the conditions for making the step unstable, such as unit test failures, findings criteria, and/or console log entries.
    Output variables (Optional) Specify the output variables to be passed to other steps down the chain. For details, see Publish output variables.

Back to top

See also: