Versions Compared

Old Version 1

changes.mady.by.user Samuel Valdez

Saved on

compared with

New Version Current

changes.mady.by.user Dan King

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Make sure link text matches link URL.

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

Table of Contents
maxLevel4
minLevel3

Step-by-step Workaround for * * AUTO Servers (e.g., SF QA AUTO)

Also see the following Bitbucket issues:

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

...

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\automation
C:\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 are important. It is recommended that the repositories be download by using a Web browser in the downloads section of each repository. It files are important, and it is important to accept the default name for the downloaded foldersnames when they are downloaded.


Tip
titleTags Tab

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
titleConvenience Bookmarks

On the SF QA AUTO machine, the following Mercurial links are already bookmarked in Firefox.


Mercurial:

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

Git:

1. https://bitbucket.org/sfgovdt/easx/downloads/?tab=tags
2. 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.

...

gz
C:\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:

Example of downloaded repository names in WindowsImage Removed

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:

Image Removed

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

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@12930
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "howto" and type = "page" and space = "MAD"
labelshowto

Related issues
Page Properties
hiddentrue
Tip
titleCapture the changeset identifiers

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:

  • eas changeset identifier (EAS_BRANCH): 4bfdbdd3aff1
  • sfeas_config changeset identifier (CONFIG_BRANCH): 8b95cae3f9b5

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
titleConvenience Boookmark

On the SF QA AUTO machine, the following Mercurial link is already bookmarked in Firefox.

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
titleBitbucket Credentials Are Not Needed

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
titleChangeset Identifiers

When prompted for the EAS_BRANCH and the CONFIG_BRANCH, paste the changeset identifiers that were saved earlier:

Image Added

Open a Command Prompt and execute the following commands:

Code Block
languagepowershell
linenumberstrue
cd C:\apps\
python eas_automation_deploy.py eas_automation

EAS source code has been successfully deployed to the target machine:

Image Added

Confirm the Deployment

The deployment can be confirmed by performing the steps that are described in Section 3 of the Testing page.