...
- 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
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. Make a remote-desktop connection (RDP) 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 | ||
|---|---|---|
| ||
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
...
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 |
...