This is amusing to know cause I have had Windows builds running just fine with a secret for several weeks now. What’s weird though is that it suddenly stopped working 4 days ago which prompted me to look for solutions.
I’ve found that if I have a secure value in my deployment: section, Windows seems to use it fine and there are no lockups at other points. However if I use a secret in the project settings or set secure env variables in my .travis.yml then Windows locks up all output as soon as i run my first external command (cinst, powershell, etc).
I’m wondering if it’s possible to set secure values later in the job rather than as top level variables available all the way through a job? Something like:
- secure: <encrypted variable>
so that the encrypted variable only gets looked at during the script phase?