Download artifact from external source

Overview of the Download artifact from external source job step, which lets you designate an external source location for downloading artifacts.

The Download artifact from external source job step lets you download artifacts from an external source. From the job step settings (Figure 1), you can customize information about the job step, including:

• A custom step name can be defined; otherwise, the default step name will be used
• External artifacts are downloaded using HTTP, based on the URL provided in the Artifact url field. This URL must be a valid URL to access artifacts.
• Save as: Provide a name under which the downloaded artifact will be saved
• HTTP request headers: Lets you pass additional information in the HTTP request, such as information used for authentication, like the API key. You can find an example and more information about using secrets in HTTP headers for downloading artifacts from an external source here.
• HTTP request options: Enables additional configuration options for the external artifact download request for external artifact download.
  • You can define destination where external artifact should be downloaded as a relative directory path within the agent's working directory. If left blank, artifact will be downloaded within the agent's working directory
  • Select which HTTP method to use: GET, POST, PUT
  • The HTTP request body field lets you specify additional JSON content, which may be required by the target API.
• Every step has Advanced options through which steps can be managed. When execution of the step fails, execution of the job continues. If option Abort job on step fail is marked, Job execution will stop once this step fails and further steps will not be executed. When it comes to skip condition, it allows skipping the current step if the condition is met.