Background
On December 01, 2018 the EAS source code version control provider, Bitbucket, disabled support of TLSv1 and TLSv1.1 and began requiring secure connections through TLS 1.2.
...
See also EAS Issue 251: Create deployment workaround for TLS 1.2 compatibility problem
Step-by-step workaround for * * WEB servers (e.g. SF QA WEB)
(Note: steps for DB and GEO servers are slightly different and will be published as/when needed.)
1. Manually download required files to a computer that has FTP access to the EAS servers
A. Download Repositories
There are three EAS repositories to download.
...
| Note |
|---|
Again, the folder names are important, so do not change them. |
Example of downloaded repository folders (compressed and uncompressed) in Windows:
B. Download Workaround Deployment Scripts
...
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 *.sh |
5. Move shell scripts to their correct locations
sudo cp deploy_eas_init.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 caaed66 ff939b9 dan-king |
7. Confirm deployment with tests
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...