Closed ryanybrennan closed 5 years ago
Fix update: Turns out that some people signed up with travis-ci.com and not travis-ci.org, which is what the original link is. Below is the travis-ci.com version of the build: https://travis-ci.com/MerryFairyTalesAD440/API/builds/103262557
The fix was simply adding the environmental variables Travis CI uses to log into Azure and deploy to Azure Functions.
Now that the environmental variables are in place, the build deploys successfully. The next build that ran on travis-ci.com on the develop branch deployed without issue.
https://travis-ci.com/MerryFairyTalesAD440/API/builds/103283850
Note: even though the deployments occur on different sites, deployments on the .com and .org sites affect the same Azure Functions repo, which is why the deployment notes state everything is up to date.
Task #25
Reported to by a member of the API team that the Travis CI deployment is failing, even though we have successfully got it deployed.
https://travis-ci.org/MerryFairyTalesAD440/API/builds/502217722