Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This operation is similar to clone, except it does not require any inputs, as values are derived from Project SCM Configurations.

Environment/Instance Properties

...

Property Name

...

Required

...

Description

...

Project Properties

...

Property Name

...

Required

...

Description

...

 

...

 

...

 

Inputs

...

Input Name

...

...

Description

...

 

...

 

...

 

Outputs

...

Output Name

...

Required

...

Description

...

 

...

 

...

 

Artifacts

This operation doesn't consume or produce any artifacts.

Endpoint Selection

This operation will select delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the environment/instancetarget.

Selecting a specific resource will result in selection of endpoints associated to the target which have that resource defined.

Endpoint Execution

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

...

The cloneProjectSources operation will perform a shallow clone using a depth value of 1. This will only grab the latest version of the code100. Revision numbers are captured by FlexDeploy prior to submit of build workflow (FlexDeploy will capture latest revision for build). If revision is not found in shallow clone copy, then plugin will gradually clone larger depth till 500. Branch, Sparse checkout folder and destination folder are used as configured in Project SCM configuration. This Keep note that this operation will also perform a checkout of the captured revision when the build was triggered. This ensures that the build code used corresponds to the FlexDeploy project version. The checked-out code is suitable for tagging and building , but is not suitable to commit and push back.

Below are the values that are used for the operation.

...