* * AUTO Server

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

Also see the following Bitbucket issues:

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.

The names of the compressed repository files are important, and it is important to accept the default names when they are downloaded.

Tags Tab

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.

Convenience 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=tags

Git:

1. https://bitbucket.org/sfgovdt/easx/downloads/?tab=tags
2. https://bitbucket.org/sfgovdt/easconfigxsf/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 look something like this (Mercurial):

C:\apps\eas_automation\temp\sfgovdt-eas-4bfdbdd3aff1.tar.gz
C:\apps\eas_automation\temp\sfgovdt-sfeas_config-8b95cae3f9b5.tar.gz

Or this (Git):

C:\apps\eas_automation\temp\sfgovdt-eas-f64599d83de5.zip

C:\apps\eas_automation\temp\sfgovdt-easconfigxsf-fcf152a4111f.zip

Again, these names are important, so do not change them.

Capture 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.

Convenience 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.

Bitbucket 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.

Changeset Identifiers

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:

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.