Using Version Control or File Systems with Eggplant Manager

An administrator must create at least one repository in Eggplant Manager. The purpose of a repository is to configure access to the location of the test files you want to use in Eggplant Manager. The test files can be in a file system or a version control system. The Eggplant Manager server must have network access to the location of the test files. For more information about creating a repository, see Creating a Repository in Eggplant Manager.

Eggplant Manager provides different options for how you can set up a repository to access your test files. One of those options is to pass commands through a command line interface (CLI).

When to Use the Command Line to Access Test Files

The CLI option is useful when your test files are in the following locations:

  • some version control systems
  • a file system on a machine where the Eggplant Manager server is not running

Version control system: If the test files you want to use in Eggplant Manager are in a version control system other than Git, Subversion, or Mercurial, you need to use the CLI option to pass the file checkout and update commands to the version control system. While Eggplant Manager has built-in support for checkout and update commands for Git, Subversion, and Mercurial, you can still use the CLI with these types of repositories if you need to use more advanced commands.

Note: You can also use the CLI option to copy files on the file system of the same computer where Eggplant Manager is running. However, Eggplant Manager provides the File System repository option specifically for this situation. See Repository Types in Creating a Repository for more information about File System repositories.

See Examples: Working with Version Control Systems for the types of commands you can pass through a CLI for Eggplant Manager repositories.

Selecting the Command Line Command Repository Type

To create an Eggplant Manager repository that uses a CLI to pass commands, you must select Command Line Command in the repository Type field when you create a repository.

Examples: Working with Version Control Systems

Below are examples of checkout and update commands you might pass through a CLI for version control systems.

Note: Some version control systems require more configuration, depending on their functionality.
Important: The following commands are only examples. The commands that you need to use are specific to your environment. They depend on what version control system you are using and the operating systems running on the computers in your environment.

svn [Subversion]

  • Checkout: svn co svn+ssh://remote.host.com/path/to/test/suite/repository/trunk

  • Update: cd trunk && svn update

Note: By default, Subversion creates a sub-directory in the repositories cache directory. Because of this, changing to that directory with a change directory cd command is required first, as shown above, before you can run the svn update command.

cvs [Control Versioning System]

  • Checkout: cvs checkout mymodule

  • Update: cvs update

Git

  • Checkout Master: git clone git@bitbucket.org:<account>/<repo_name.git 2>&1
  • Update Master: cd <repo_name> && git pull -f git@bitbucket.org:<account>/<repo_name.git 2>&1
  • Checkout Branch: git clone -b <branchName> git@bitbucket.org:<account>/<repo_name.git 2>&1
  • Update Branch: cd <repo_name> && git pull -f git@bitbucket.org:<account>/<repo_name.git <branchName> 2>&1
Note: By default, Git creates a sub-directory in the repositories cache directory. Because of this, changing to that directory with a change directory cd command is required first, as shown above, before you can run the git pull command.

 

This topic was last updated on September 07, 2020, at 09:39:31 AM.

Eggplant icon Eggplantsoftware.com | Documentation Home | User Forums | Support | Copyright © 2020 Eggplant