...
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:
eas/automation/eas_automation_deploy.py
To:
C:\apps
Run the Deployment Script
Everything is now in place to run 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:
|
...
| 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.
...