GoPublishBinary

GoPublishBinary - Tags

JFrog Pipelines Documentation

Products

JFrog Pipelines

Content Type

User Guide

ft:sourceType

Paligo

This topic lists tags that can be used with GoPublishBinary Pipeline steps. For more information on GoPublishBinary Pipeline steps, see GoPublishBinary.

name

An alphanumeric string (underscores are permitted) that identifies the step.

type

Must be GoPublishBinary for this step type.

configuration

Specifies all configuration selections for the step's execution environment. This step inherits the Bash/ PowerShell step configuration tags, including these pertinent tags:

Tag	Description of usage	Required/Optional
`integrations`	Specifies an Artifactory Integration or JFrog Platform Access Token Integration. Required when `autoPublishBuildInfo`is set to false. Otherwise, the artifactory integration specified in the BuildInfo resource will be used.	May be required
`outputResources`	Must specify a BuildInfo resource when`autoPublishBuildInfo`is set to true. If `JFROG_CLI_BUILD_NAME` or `JFROG_CLI_BUILD_NUMBER` is set as an environment variable for the pipeline or the input GoBuild step, that name and/or number is used for the output BuildInfo. Otherwise, the default `buildName` and `buildNumber` are `$pipeline_name` and `$run_number` respectively.	May be required
`inputSteps`	Must specify a GoBuild, Bash, or PowerShell step.	Required

Tag

Description of usage

Required/Optional

integrations

Specifies an Artifactory Integration or JFrog Platform Access Token Integration. Required when autoPublishBuildInfois set to false. Otherwise, the artifactory integration specified in the BuildInfo resource will be used.

May be required

outputResources

Must specify a BuildInfo resource whenautoPublishBuildInfois set to true.

If JFROG_CLI_BUILD_NAME or JFROG_CLI_BUILD_NUMBER is set as an environment variable for the pipeline or the input GoBuild step, that name and/or number is used for the output BuildInfo. Otherwise, the default buildName and buildNumber are $pipeline_name and $run_number respectively.

May be required

inputSteps

Must specify a GoBuild, Bash, or PowerShell step.

Required

In addition, these tags can be defined to support the step's native operation:

Tags derived from Bash

All native steps derive from the Bash step. This means that all steps share the same base set of tags from Bash, while native steps have their own additional tags as well that support the step's particular function. So it's important to be familiar with the Bash step definition, since it's the core of the definition of all other steps.

Tag	Description of usage	Required/Optional
`forceXrayScan`	When true, forces a scan of the pushed image by JFrog Xray. Default is false.	Optional
`failOnScan`	When set to t`rue`, and when the Xray Policy Rule Fail Build checkbox is checked in the Configure a Security Rule window, a failed Xray scan will result in a failure of the step.Configure a Security Rule Default is `true`.	Optional
`autoPublishBuildInfo`	When set to `true`, publishes build info with the Docker image. Default is `false`.	Optional
`targetRepository`	Repository in Artifactory where the module will be published.	Required
`failOnValidate`	Fail the step if signatures of build artifacts cannot be verified. Default is `false`.	Optional (Signed Pipelines must be enabled)

execution

Declares collections of shell command sequences to perform for pre- and post-execution phases:

Tag	Description of usage	Required/Optional
`onStart`	Commands to execute in advance of the native operation	Optional
`onSuccess`	Commands to execute on successful completion	Optional
`onFailure`	Commands to execute on failed completion	Optional
`onComplete`	Commands to execute on any completion	Optional

The actions performed for the onExecute phase are inherent to this step type and may not be overridden.