| 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
Step-by-step Workaround for * * AUTO Servers (e.g., SF QA AUTO)
1. Manually download required files to a computer that has FTP access to the EAS servers
A. Download Repositories
...
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 folders files are important. It is recommended that the repositories be download by using a Web browser in the |
| Tip | ||
|---|---|---|
| ||
The Tags tab will let you select which changeset, and format, that you want to download. | ||
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 |
Mercurial:
1. https://bitbucket.org/sfgovdt/eas/downloads/?tab=tags
2. https://bitbucket.org/sfgovdt/sfeas_config/downloads/?tab=tags
Git:
1. https://bitbucket.org/sfgovdt/easx/downloads/?tab=tags
32. https://bitbucket.org/sfgovdt/thirdpartyeasconfigxsf/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 be named look something like these:
...
this (Mercurial):
C:\apps\eas_automation\temp\sfgovdt-eas-
...
4bfdbdd3aff1.tar.
...
gzC:\apps\eas_automation\temp\sfgovdt-sfeas_config-
...
Uncompress the files.
This will result in three folders, such as these:
sfgovdt-eas-caaed66d58b3
sfgovdt-sfeas_config-ff939b913451
sfgovdt-thirdparty-8a1b00afcb15
...
8b95cae3f9b5.tar.gz
Or this (Git):
C:\apps\eas_automation\temp\sfgovdt-eas-f64599d83de5.zip
C:\apps\eas_automation\temp\sfgovdt-easconfigxsf-fcf152a4111f.zip
| Note |
|---|
Again, these names are important, so do not change them. |
Example of downloaded repository folders (compressed and uncompressed) in Windows:
B. Download Workaround Deployment Scripts
Download the latest version of these five files from the /eas/web/bin/ source folder
https://bitbucket.org/sfgovdt/eas/src/default/web/bin/
1. deploy_eas_init.sh
2. deploy_eas_source.py
3. deploy_eas.sh
4. set_eas_mode.sh
5. set_eas_env.sh
2. FTP the 3 folders and 5 files to the /var/tmp folder of the server(s) to be deployed
Example of uploading the files from Windows to the /var/tmp directory of the target server using FTP tool FileZilla:
See also https://filezilla-project.org/
See also PuTTY and SSH
3. Connect to relevant server and browse to /var/tmp
cd /var/tmp |
4. Change permissions of shell scripts
...
sudo chmod u+x *.sh5. Move shell scripts to their correct locations
...
sudo cp deploy_eas_init.sh /var/www/html
sudo cp deploy_eas_source.py /var/www/html
sudo cp deploy_eas.sh /var/www/html
sudo cp set_eas_mode.sh /var/www/html
sudo cp set_eas_env.sh /var/www/html| Note |
|---|
Leave the 3 repository folders in the directory |
6. Run the deployment script as sudo
...
cd /var/www/html
sudo ./deploy_eas_init.sh <EAS_COMMIT> <CONFIG_COMMIT> <BITBUCKET_USER>...
sudo ./deploy_eas_init.sh caaed66 ff939b9 dan-king |
7. Confirm deployment with tests
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
| 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. Perhaps the easiest way to do this is to navigate to the workaround deployment script file in the repository with a browser on the target machine, invoke the "... → Open raw" menu command, and then save the file in the directory that is specified below.
| Tip | ||
|---|---|---|
| ||
On the |
From:
Mercurial:
• https://bitbucket.org/sfgovdt/eas/src/default/automation/eas_automation_deploy.py
Git:
• https://bitbucket.org/sfgovdt/easx/src/master/automation/eas_automation_deploy.py
To:
C:\apps
Run the Deployment Script
Everything is now in place to deploy 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 for the EAS_BRANCH and the CONFIG_BRANCH, 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 |
EAS source code has been successfully deployed to the target machine:
Confirm the Deployment
The deployment can be confirmed by performing the steps that are described in Section 3 of the Testing page.