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 * * WEB servers (e.g. SF QA WEB)
...
)
1. Manually download required files to a computer that has FTP access to the EAS servers
...