Home → Suggestions →

Add "import YAML file" option to project settings

• Edit

sbohlen

11 Jan, 2015 09:14 PM

When troubleshooting build settings and/or exploring Appveyor config options for projects that have a YAML file, it would be valuable to have an "import YAML" option in the dashboard (that provides the inverse operation of "export YAML").

As is the case now, I have to commit multiple updates to the YAML file in order to experiment with the effect of changes to project settings, thrashing the repository with a LOT of CI-centric commits to the YAML file. I'd prefer to make the changes in the dashboard and kick off a build 'manually' in order to observe the changes (and then transpose these changes to the YAML file once I'm happy with them so that they are persisted in my repo).

Its true that the "ignore YAML" setting option in the dashboard *sort of* meets this need in that I can enable this option temporarily and then make an experimental change to the settings via the dashboard. However, once I enable this option, I then have to painstakingly reproduce each of the settings currently in the YAML file as a starting point for my subsequent experimentation. This is both tedious and error-prone (for me, at least!)

If there were an "import YAML" option in the dashboard, my process could be as follows ...

1. start with a project having a YAML file
2. import the YAML file into the Appveyor dashboard for the project
3. enable the "ignore YAML" option
4. make settings changes via the dashboard, firing off 'manual builds' to observe/evaluate the affect of the changes
5. repeat step 4 as many times as necessary
6. once satisfied with the changes, use the "export YAML" option to acquire another copy of new acceptable settings
7. commit that YAML to the repo, overwriting the old YAML file
8. clear the checkbox in the dashboard for "ignore YAML"

This would make the process of iterating through the change-setting -> run build -> evaluate results cycle more independent of thrashing the repo with multiple commits to the YAML file as one works to refine their build settings/scripting for a project. If the above process were supported, unlimited experimentation with the settings could be condensed into just a single (final) update to the YAML file in the repo.

Thanks in advance for your consideration of this suggestion!

-Steve B.

1. 1 Posted by gep13 on 12 Jan, 2015 07:41 AM

   

   Hello,

   Just a thought, but couldn't you simply do the following...

   1. Start a new project
      
   2. Immediately do an export of the YAML file
      
   3. enable the "ignore YAML" option
      
   4. make settings changes via the dashboard, firing off 'manual builds' to observe/evaluate the affect of the changes
      
   5. repeat step 4 as many times as necessary
      
   6. once satisfied with the changes, use the "export YAML" option to acquire another copy of new acceptable settings
      
   7. commit that YAML to the repo, overwriting the old YAML file
      
   8. clear the checkbox in the dashboard for "ignore YAML"

   i.e. I don't really see the need for an import option, unless you already have some settings defined, but if you are starting a new project, how would you already have this?

   Gary

   • Edit

2. 2 Posted by sbohlen on 12 Jan, 2015 09:17 PM

   

   Yes, your suggestion works fine so long as we're talking about a NEW project setup scenario. However, the real value (for me!) of the import YAML option would be my ability to iterate back and forth between the YAML file and the dashboard settings over the life of the project.

   Simple scenario: I'm running a build (but no tests) controlled from the YAML file. Now its a month later and I want to enable tests but need to experiment with some combination of include/exclude of test categories in order to get only the tests running that i know are really ready to pass (e.g., imagine I have some integration tests that need something not available on Appveyor).

   In this scenario I need to transpose all the values from the YAML file to the dashboard before I can then start to experiment with getting the category filters configured properly before returning to using the YAML file again via a new export of the file.

   Does that make sense --?

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 12 Jan, 2015 11:03 PM

   

   You can easily use REST API for doing that: http://www.appveyor.com/docs/api/projects-builds#update-project-set...

   Poster, Fiddler, CURL - anything for sending requests could work.

   • Edit

4. 4 Posted by sbohlen on 12 Jan, 2015 11:19 PM

   

   Ha -- perfect! I hadn't considered to look there; thanks, that will suit me just fine!

   Cheers,

   -Steve B.

   • Edit

5. 5 Posted by micah on 13 Jan, 2016 07:03 AM

   

   Link broke, here is a fixed one: http://www.appveyor.com/docs/api/projects-builds#update-project-set...

   • Edit

6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:03 AM.