uploadArtifact2 (Nexus)

This operation provides an easy way to upload an artifact to Nexus Repository Manager from FlexDeploy artifact repository or any current file system directory. This can be used in FlexDeploy build workflows to upload the generated Project Build to Nexus repository if required.

Nexus Account Properties

Property Name

Property Code

Required

Description

Property Name

Property Code

Required

Description

Nexus URL

FDNEXUSACCT_URL

Yes

The URL of Nexus Repository Manager (e.g. http://[host]:[port]).

Nexus Username

FDNEXUSACCT_USERNAME

Yes

User to connect to Nexus as.

Nexus Password

FDNEXUSACCT_PASSWORD

Yes

The password for the Nexus User.

Inputs

Input Name

Input Code

Required

Description

Input Name

Input Code

Required

Description

Nexus Account

FDNEXUS_INP_NEXUS_ACCOUNT_CODE

Yes

The Nexus account with all the required properties like Instance Url, Username, and Password for running Nexus Instance. Configure this under Topology - Integrations - Artifact Repository.

Nexus Version

FDNEXUS_VERSION

Yes

The version of Nexus Repository Manager being used. (Nexus 3.X or Nexus 2.X)

Nexus Path

FDNEXUS_PATH

Yes

Path to upload an artifact in Nexus. (e.g. releases/artifactId/1.1/)

Nexus Repository

FDNEXUS_REPOSITORY

Yes

Identifier of the Nexus repository. Repository ID for Nexus 2, repository name for Nexus 3.

  • If using Nexus 2, then repository id is in URL after FDNEXUS_URL/nexus/content/repositories/FDNEXUS_REPOSITORY.

  • If using Nexus 3, then repository name is in URL after FDNEXUS_URL/repository/FDNEXUS_REPOSITORY.

Upload From Directory

FDNEXUS_UPLOAD_FROM_DIR

No

Specify the Path from which the Artifact can be uploaded to Nexus. If no inputs given, the default Artifacts dir will be used.

Artifacts

This operation produces artifacts that will be stored in the artifact's repository.  

Endpoint Selection

This operation will select all available endpoints associated to the target.  

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

The following macros are not currently supported in the footer:
  • style