Page Comparison

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.

The EAS stack does not currently support TLS 1.2 (as of December 2018). While this issue is being resolved there is a workaround for deploying EAS source code.

See also EAS Issue 251: Create Also see the following Bitbucket issues:

• EAS-251 : Create deployment workaround for TLS 1.2 compatibility problem
• EAS-254 : Create an automated deployment workaround for TLS 1.2 compatibility problem

Step-by-step workaround for

...

<environment>_WEB servers (e.g. SF_QA_WEB)

...

Substitute <environment> with one of the relevant environments: SF_DEV, SF_QA, SF_PROD, SD_PROD

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.

...

Mercurial:

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

Git:

1. https://bitbucket.org/sfgovdt/easx/downloads/?tab=tags

...

2. https://bitbucket.org/sfgovdt/easconfigxsf/downloads/?tab=tags

3. https://bitbucket.org/sfgovdt/thirdpartyx/downloads/?tab=tags

Unzip the three downloaded zip files.

Extract the contents of each unzipped folder.

Example folder names

Mercurial:

            sfgovdt-eas-caaed66d58b3.zip
            sfgovdt-sfeas_config-ff939b913451.zip
            sfgovdt-thirdparty-8a1b00afcb15.zip

Uncompress the files.

...

Git:
            sfgovdt-easeasx-caaed66d58b37a7a6ad72b0f
            sfgovdt-sfeas_configeasconfigxsf-ff939b913451bd73cd53771c
            sfgovdt-thirdpartythirdpartyx-8a1b00afcb1508f69eb30d1a

 Note
Again, the folder names are important, so do not change them.
Example of downloaded repository folders (compressed and uncompressed) in Windows:
Image Removed

B. Download Workaround Deployment Scripts
Download the latest version of these five files from the /eas/web/bin/ source folder.
Mercurial: https://bitbucket.org/sfgovdt/eas/src/default/web/bin/
Git: https://bitbucket.org/sfgovdt/easx/src/master/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 (via Mercurial):
Image RemovedImage Added

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
  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 /var/tmp/
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
The deployment can be confirmed by performing the steps that are described in Section 3 of the Testing page.
Related articles
 Filter by label (Content by label)
showLabels
false
max
5
spaces
com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@12930
showSpace
false
sort
modified
reverse
true
type
page
cql
label = "howto" and type = "page" and space = "MAD"
labels
howto
...