If I look in the setting for the Travis project, it does not show my secret environment keys. It’s like Travis periodically is unable to establish that I have secret keys on this project. I have definitely provided them as Travis has been able to execute these steps in the past (just an hour previous as I linked).
I’ve been seeing this issue over the last week or two on this repo.
It may be unrelated, but I’ve also gotten email notifications about a failed job and when I follow the link it takes me to a job that shows successful.
The symptoms seem like Travis is spawning up multiple instances of a job and then deciding which one to keep as the “authoritative” result.
I assure you that an hour ago when I opened this conversation, the Environment Variables section of Settings was blank, and I changed no project settings or travis configs in Travis on any project in the interim. The only thing that happened in the interim was that another build was triggered.
If I navigate to Settings from the failed build, the Environment Variables section is unpopulated.
If I navigate to Settings from the passing build, the Environment Variables section is correctly populated.
The difference seems to be URL. The failing job and missing settings is on travis-ci.com and the passing job with correct settings is on travis-ci.org.
If there are 2 different profiles for my project, on on .com and one on .org that would explain the symptoms I’m seeing, as there would be inherent race conditions between the two. I certainly did not create the profiles twice, and am unsure on the proper way to clean this up.
