| Table of Contents | ||||
|---|---|---|---|---|
|
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
Remove the Target Directories
Make a remote-desktop connection (RDP) to the target machine, and remove, or rename, the following directories. The deployment will create new, updated ones:
C:\apps\eas_automation\automationC:\apps\eas_automation\database
Manually Download the Required Files
Download the Repositories
There are two EAS source code repositories to download to the target machine.
| Note |
|---|
The names of the compressed repository files are important, and it is important to accept the default names when they are downloaded. |
| Tip | ||
|---|---|---|
| ||
Download the repositories in gzip format (.gz, .tar.gz) with a Web browser by navigating to the Downloads section of each EAS source code repository. The Tags tab in the Downloads section of a given repository contains links for each of the changesets, and formats, that are available to download. |
| Tip | ||
|---|---|---|
| ||
On the |
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.gzC:\apps\eas_automation\temp\sfgovdt-sfeas_config-8b95cae3f9b5.tar.gz
| Note |
|---|
Again, these names are important, so do not change them. |
| Tip | ||
|---|---|---|
| ||
You will be prompted for the changeset identifiers from each of the repositories, so it is a good idea to have them ready by copying them into a text file. Using the compressed repository files from above, these would be the corresponding changeset identifiers:
|
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.
| Tip | ||
|---|---|---|
| ||
The deployment script will prompt you for Bitbucket credentials, but this workaround does not require them so it is okay to accept the default values for USER, Password, and TEAM. This is illustrated in the next Tip. |
| Tip | ||
|---|---|---|
| ||
When prompted, paste the changeset identifiers that were saved earlier:
|
Open a Command Prompt and execute the following commands:
| Code Block | ||||
|---|---|---|---|---|
| ||||
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.