This strategy populates the artifact repository using the content of the Root Directory after filling it by exporting data from an ARCAD version.

This strategy executes an ARCAD macro-command to prepare a SAVF to import into the artifact repository. This command must be executed on an ARCAD Server that runs on an IBM i platform.

First, the system connects to the ARCAD Server using the connection information defined in the import strategy. Then, the defined macro-command is executed:

1. the version number is resolved,
2. the variables are substituted,
3. the execution of the macro-command is submitted using the defined submission parameters.

The system waits for the end of the submitted job and returns the execution result. If the execution is OK, a stream file is created from the target SAVF file into the temporary IFS directory. This stream file is downloaded into the Root Directory defined by the strategy and the content of the Root Directory is imported as artifacts.

Save the changes (, Ctrl+S or File > Save).

This strategy includes most of the same properties as the generic ARCAD import strategy, however you do not need to define the ARCAD Application property because this value is now defined at the component level in the extended configuration. This strategy should, therefore, be used in ARCAD-type components.

The Target Version Number can now be defined using a version selector to avoid making mistakes. The retrieved version list is based on:

• The ARCAD development server connection defined in the ARCAD Settings (Connecting to the ARCAD development server)
• The ARCAD Application Code defined in the parent component

Save the changes (, Ctrl+S or File > Save).

This strategy populates the artifact repository using the content of the Root Directory after filling it by executing a user-defined command.

This strategy scans defined directories and retrieves their contents according to the command defined.

To define the command to execute, configure the name and parameters of the executable command and the connection information required to access a 3rd party artifact provider via the command line.

The following properties/substitution variables can be called into the extended configuration of an import strategy or a import strategy template:

• any user-defined property in an application
• the ${activity.[activityID].component.code} substitution variable
• any user-defined property in an import strategy

To define a property, click the  Create button in the Extended Properties. Define the Key and Value of the property in the dialog. To edit an existing property, double-click it, or select it, then click the  Edit button.

To delete a property, select it, then click the  Delete button.

Save the changes (, Ctrl+S or File > Save).

This strategy populates the artifact repository using the content of the Root Directory after filling it by exporting data from a CVS repository.

Define connection properties specific to this strategy and the external CVS tool in the CVS Repository Connection Properties section. These properties are used to pass connection information to the CVS command line when the import process begins.

The following properties/substitution variables can be called into the extended configuration of an import strategy or a import strategy template:

• any user-defined property in an application
• the ${activity.[activityID].component.code} substitution variable
• any user-defined property in an import strategy

To define a property, click the  Create button in the Extended Properties. Define the Key and Value of the property in the dialog. To edit an existing property, double-click it, or select it, then click the  Edit button.

To delete a property, select it, then click the  Delete button.

Save the changes (, Ctrl+S or File > Save).

This strategy populates the artifact repository using content from one or several folders found on the same machine as the DROPS Server. It scans the directory(ies) and retrieves content according to the filters defined.

In the dialog to create or edit a File System strategy, the root path to the directory in which your artifacts are stored is defined. To filter the defined path and tell DROPS to import only certain artifacts instead of everything found in the root path, define a regular expression that filters which files to import.

There are two ways to filter by the last date artifacts were modified:

1. define a range of dates: all the files that have a last modification date in this range will be imported.
2. define a date limit: all the files that have a last modification date before this date will be imported. This date limit is computed by subtracting time from the execution date. To define this date, enter the amount of time to subtract and also the time (day, minute or hour).

To create a File System strategy filter, click the  Create button in the File System strategy manager and define the directory to scan and the filters to apply.

To edit an existing filter, double-click it, or select it, then click the  Edit button.

To delete a filter, select it, then click the  Delete button.

Save the changes (, Ctrl+S or File > Save).

This strategy populates the artifact repository using the content of the Root Directory after filling it by exporting data from a Git repository.

This strategy executes the GIT checkout command to reach a GIT repository.

Artifacts are exported from a GIT repository when DROPS executes the following command. When the necessary connection information is defined, DROPS uses the information to create and send the fully-defined command to the GIT.

#Local Git Repository Preparation
git clone https://username:password@git-repository-url target-export-path
git --git-dir="target-export-path.git" 
    --work-tree="target-export-path" 
    fetch
    --tag

#Modification retrieval for a given tag
git --git-dir="target-export-path.git" 
    --work-tree="target-export-path" 
    checkout
    tags/particular-tag

Define connection properties specific to this strategy and the external GIT tool in the GIT Repository Connection Properties section. These properties are used to pass connection information to the GIT command line when the import process begins.

The following properties/substitution variables can be called into the extended configuration of an import strategy or a import strategy template:

• any user-defined property in an application
• the ${activity.[activityID].component.code} substitution variable
• any user-defined property in an import strategy

To define a property, click the  Create button in the Extended Properties. Define the Key and Value of the property in the dialog. To edit an existing property, double-click it, or select it, then click the  Edit button.

To delete a property, select it, then click the  Delete button.

Save the changes (, Ctrl+S or File > Save).

This strategy populates the artifact repository using the content of the Root Directory after filling it by exporting data from an IBM i repository.

This strategy is intended to retrieve and import existing SAVF files from an IBM i that match the provided Save File Name Pattern defined in the List of Save Files section. Regex can be entered in this section.

DROPS connects to the target IBM i using the provided system, login and password. It will eventually set the iASP for the connection if one is defined (and different from *SYSBAS).

DROPS will first transfer each SAVF file found to the temporary IFS directory defined (using the CPYTOSTMF IBM i command), and then copy them to the artifact repository.

To define a SAVF file, click the  Add button in the List of Save Files manager.

To edit an existing SAVF file, double-click it, or select it, then click the  Edit button.

To delete a SAVF file from the list, select it, then click the  Remove button.

Save the changes (, Ctrl+S or File > Save).

This strategy populates the artifact repository using the content of the Root Directory after filling it by exporting data from an SVN repository then following the standard process.

This strategy executes the SVN export command to reach an SVN repository.

Artifacts are exported from an SVN repository when DROPS executes the following command. When the necessary connection information is defined, DROPS uses the information to create and send the fully-defined command to the SVN.

    svn export [-r revision]
               [--ignore-externals]
               [--depth ARG]
               [--force]
               [--ignore-keywords]
               [--native-eol ARG]
               [--quiet]
               svn-repository-url
               target-export-path
               --username username
               --password password
               --non-interactive

Define connection properties specific to this strategy and the external SVN tool in the Connection Information section. These properties are used to pass connection information to the SVN command line when the import process begins.

Define properties specific to this strategy in the Extended Properties section. These properties can be used to add options to the connection command.

1. If a property contains a key called --force and the value is blank, the option --force will be added to the command parameter.
2. If a property contains a key called --native-eol and the value is CRLF, the option --native-eol CRLF will be added to the command parameter.

To define a property, click the  Create button in the Extended Properties. Define the Key and Value of the property in the dialog. To edit an existing property, double-click it, or select it, then click the  Edit button.

To delete a property, select it, then click the  Delete button.

Save the changes (, Ctrl+S or File > Save).