tag:help.appveyor.com,2012-11-13:/discussions/questions/3671-suggeston-upload-appveyorymlAppVeyor: Discussion 2018-08-25T02:20:53Ztag:help.appveyor.com,2012-11-13:Comment/423706032017-04-16T22:51:48Z2017-04-16T22:51:48ZSuggeston: Upload appveyor.yml<div><p>I have a local appveyor.yml in my repo but I notice it appears out of sync with the hosted settings in appveyor - woudl it be possible to upload my local appveyor.yml file to appveyor and reses/synchronise the two?</p>
<p>Shaun</p></div>shaun_wildetag:help.appveyor.com,2012-11-13:Comment/423706032017-04-17T16:35:51Z2017-04-17T16:35:51ZSuggeston: Upload appveyor.yml<div><p>Hi Shaun,</p>
<p>I afraid there is some misunderstanding here. There is not such thing as hosted <code>appveyor.yml</code> setting. AppVeyour reads settings from <code>appveyor.yml</code> which is in repository before every build. If you have <code>appveyor.yml</code>, it takes over UI, unless you check <code>ignore appveyor.yml</code> or set custom and non-existing YAML file name in UI. Another possible issue is if you chose repository type <code>Git</code> instead of <code>GitHub</code> or <code>BitBucket</code>, because generic Git cannot read individual files from repo. More information is <a href="https://www.appveyor.com/docs/build-configuration/#configuring-build">here</a></p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/423706032017-04-18T06:06:06Z2017-04-18T06:06:06ZSuggeston: Upload appveyor.yml<div><p>Hi Ilya</p>
<p>What I mean is to reset the UI settings with the updated appveyor.yml so that all the UI settings are replaced by their equivalents in the uploaded yml – the end effect being that if I then attempted to download the appveyor.yml via the UI I would have the same file.</p>
<p>This way when a user wants to update their yml file they can upload their current one, make changes in the UI and the download the yml again.</p>
<p>I think this is a lot safer than making changes in the UI and then cut and pasting the bits into a local yml file (where errors can occur).</p>
<p>I hope I have made my request clearer.</p>
<p>Shaun</p></div>shaun_wildetag:help.appveyor.com,2012-11-13:Comment/423706032017-11-01T22:38:01Z2017-11-01T22:38:02ZSuggeston: Upload appveyor.yml<div><p>Thats a good point. Keeping the UI Settings and the appveyor.yml in the repo in sync is pain at the moment. My scenario is:<br>
1. I want to use the UI to configure everything<br>
2. I want to versioning and maybe distribute / reuse my settings in different repos -> therefore i export the yml and check it in whenever i make changes in the UI<br>
-> thats already a pain, would be good if that could be automated 3. When I want to do a small change in the yml file, i have to do the same change in the UI to keep both in sync, otherwise the change would get lost when I do an Export of the apveyor.yml next time</p></div>Thomastag:help.appveyor.com,2012-11-13:Comment/423706032017-11-01T23:18:15Z2017-11-01T23:18:15ZSuggeston: Upload appveyor.yml<div><p>We understand this. Problem is that some features like <a href="https://www.appveyor.com/docs/build-configuration/#exclude-configuration-from-the-matrix">Exclude configuration from the matrix</a> or <a href="https://www.appveyor.com/docs/branches/#sharing-common-configuration-between-branches">Sharing common configuration between branches</a>, to name a few, are very difficult to be expressed in UI. I mean if you try to keep UI simple and clean. We consider UI a good starting point and assume that for more advanced configuration people will go for YAML. Also please note that use YAML from <a href="https://www.appveyor.com/docs/build-configuration/#alternative-yaml-file-location">remote location</a> if you have same configuration for different project and want to avoid duplication.</p></div>Ilya Finkelshteyn