tag:help.appveyor.com,2012-11-13:/discussions/questions/1728-register-xamarin-license-for-pull-requestsAppVeyor: Discussion 2018-10-19T08:17:30Ztag:help.appveyor.com,2012-11-13:Comment/380989102015-10-04T09:41:44Z2015-10-04T17:52:33ZRegister Xamarin license for pull requests<div><p>I would like Xamarin projects also to be built in builds
triggered by pull requests.<br>
I see secure environment variables are disabled for such
builds.<br>
Is it possible to register the Xamarin license for these
builds?<br>
Exposing the password is of course not an option :-)</p></div>Oystein Bjorketag:help.appveyor.com,2012-11-13:Comment/380989102015-10-05T17:25:42Z2015-10-05T17:25:42ZRegister Xamarin license for pull requests<div><p>If it's private project/repo you can "Enable secure variables
for PR builds".</p>
<p>Other than that the problem is interesting indeed and we should
give it a thought. I added a new issue: <a href="https://github.com/appveyor/ci/issues/443">https://github.com/appveyor/ci/issues/443</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/380989102015-10-05T19:04:47Z2015-10-05T19:04:47ZRegister Xamarin license for pull requests<div><p>Yes, please give it a thought! It would be great if we could set
the Xamarin license and enable Android/iOS from the AppVeyor
portal!<br>
I worked around the problem by using "IF DEFINED xamarin_password
appveyor RegisterXamarinLicense..." and building a different
solution for pull requests:<br>
<a href="https://github.com/oxyplot/oxyplot/blob/develop/appveyor.yml">https://github.com/oxyplot/oxyplot/blob/develop/appveyor.yml</a><br>
But this means we may get Xamarin build surprises after a PR has
been merged...</p></div>Oystein Bjorke