...
FlexDeploy utilizes an agentless architecture to connect to computers across private or public networks/clouds to execute build and deploy operations. This architecture uses a secured communication protocol (SSH) and eliminates the need for installing and managing software on every build and deployment target. In many cases no setup is required on an endpoint Endpoint prior to configuring it within FlexDeploy. The following details the requirements for FlexDeploy endpoint systems.
Endpoint Requirements
- Requires a Unix or Microsoft Windows operating system.
- For Microsoft Windows, must have Cygwin installed, along with the openssh package. See the Cygwin Installation Guide for more information.
- Requires JDK 1.6 or higher to be installed.
- Requires a user account which FlexDeploy can connect with.
- Requires a directory which is writable by the user account that FlexDeploy connects with.
- The FlexDeploy server must be able to access the SSH port (default is port 22) on the Endpoint.
...
See the following links for information on creating endpointsEndpoints.
Activating and Inactivating Endpoints
To inactivate an endpoint Endpoint select an existing endpoint Endpoint and click the Inactivate button. The endpoint Endpoint will not be displayed if the criteria for Active is set to "No". To reactivate an endpointEndpoint, select the desired endpoint Endpoint and click the Edit button. Then change the drop down menu for active to "Yes" and click Save. This endpoint Endpoint is now active in the system again and ready for use.
...
The structure of the configured base directory on an endpoint Endpoint is as follows:
plugins
The plugins directory holds each version of a plugin that has been utilized on the endpointEndpoint. There can be several different plugins loaded and many versions of a given plugin.
security
The security directory holds information related to the SSH connection between the FlexDeploy server and the endpoint Endpoint server and is used for secure communications.
work
The work directory contains every invocation of a plugin operation that has occurred on the endpointEndpoint. There is additional file structure under the work directory based on the execution project id and the current execution id of the given project.
...