* * AUTO Server

Step-by-step Workaround for * * AUTO Servers (e.g., SF QA AUTO)

Also see the following Bitbucket issues:

• EAS-261 : Create deployment workaround for TLS 1.2 compatibility problem
• EAS-266 : Create an automated deployment workaround for TLS 1.2 compatibility problem

Manually Download the Required Files

Download the Repositories

There are two EAS source code repositories to download to the target machine.  Make a remote-desktop connection (RDP) to the target machine.

1. https://bitbucket.org/sfgovdt/eas/downloads/?tab=tags
2. https://bitbucket.org/sfgovdt/sfeas_config/downloads/?tab=tags

Create the following directory on the target machine, and then download the repositories to it:

C:\apps\eas_automation\temp

The downloaded, compressed repository files will look something like this:

C:\apps\eas_automation\temp\sfgovdt-eas-4bfdbdd3aff1.tar.gz
C:\apps\eas_automation\temp\sfgovdt-sfeas_config-8b95cae3f9b5.tar.gz

Download the Workaround Deployment Script

If the following file has changed since the previous deployment, then it will need to be downloaded from the Source section of its repository as well.

From:

eas/automation/eas_automation_deploy.py

To:

C:\apps

Run the Deployment Script

Everything is now in place to run normally.

cd C:\apps\
python eas_automation_deploy.py eas_automation

Confirm the Deployment

The deployment can be confirmed by performing the steps that are described in Section 3 of the Testing page.

Related articles