Versions Compared

Old Version 9

changes.mady.by.user Dan Reynebeau

Saved on

compared with

New Version Current

changes.mady.by.user Chandresh Patel

Saved on

Key

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

FlexDeploy utilizes an agentless architecture to connect to computers across private or public networks/clouds to execute build and deploy operations. This architecture provides 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 prior to configuring it within FlexDeploy. The following details the requirements for FlexDeploy endpoint systems.

  • 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.

...

Viewing Endpoints

To view the configured Endpoints, select Topology -> Endpoints from the menu. Enter any optional search criteria and click the Search button.

...


It is typical to use the default file name and location to store the private key (which is in the .ssh subfolder of the user's home directory). You can optionally secure the private key file with a passphrase. It is an SSH requirement that the private key be readable only by its owner (e.g. oracle in the example above). So you must change the permissions accordingly (e.g. chmod 600 /home/oracle/.ssh/id_rsa). You will receive an error at connection time similar to the following if you omit this step.

Permissions 0777 for '/home/oracle/.ssh/id_rsa' are too open.

It is recommended that your private key files are NOT accessible by others.
This private key will be ignored.

The /home/oracle/.ssh folder on the endpoint must have drw------- permissions (eg. chmod 700 /home/oracle/.ssh)

...


The public key can also be copied to the endpoint's authorized_keys file using the Upload Public Key button.



Validate that the derived name and location of the public key is correct, and enter the password for the Endpoint connection user (if not already provided on the Endpoint definition). Click the Upload button to upload the public key to the Endpoint.

...