Home → Questions →

Multiple sln's per Repo.

• Edit

Pure Krome

29 Jan, 2015 11:33 PM

Hi

we have a private repo that contains about 5 different SLN's. We have 3 websites, 1 API (website) and some azure cloud services. We've split up the codebase into these separate sln's so our build times and unit test times are smaller.

Can we create a 'project' per sln? Right now, we have 1x appveyor.yml file in the root of our repo, sitting side-by-side the 5 .sln files. On the AV website, under project->settings, I can see a section where we can define the sln file.

So - can I create 5 projects in AV, change/set the sln file name in each project ... and each project will use the -same- appveyor.yml file AND target that specific sln only?

I'm asking this because I thought i read in the docs that the UI-Settings and the .yml file are mutually exclusive, meaning, if i have a setting in one, it won't use the settings in the other? Or did i misunderstand something, again?

1. Support Staff 1 Posted by Feodor Fitsner on 29 Jan, 2015 11:57 PM

   

   Right, you can't setup multiple projects this way as with appveyor.yml you should specify solution name in it. If you want to implement scenario like you described you should stick to UI.

   -Feodor

   • Edit

2. 2 Posted by Pure Krome on 30 Jan, 2015 12:01 AM

   

   Ok, so I need to use the UI for each project I setup then.

   Two more questions.

   1. Is it possible to import an .yml file, to auto populate the UI settings?
      
   2. Would you consider the option of a project having an optional setting: appveyor yaml file. So this means, I can create 5 .ymls and then have each project first check that setting and load that yml file, if found. Even a simple convention -> have an appveyor yaml file named the same as the solution.
      eg. myProject_A.sln => myProject_A.yml / foo.sln => foo.yml, etc
   • Edit

3. 3 Posted by Pure Krome on 30 Jan, 2015 12:02 AM

   

   Oh - one more q. if there's UI settings AND a yml file, which one is used? UI > file?

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 30 Jan, 2015 01:46 AM

   

   YAML wins unless you check "Ignore appveyor.yml" on General tab of project settings.

   Idea with multiple YML per project is nice. We have such an item in our TODO.

   You can import using REST API: http://www.appveyor.com/docs/api/projects-builds#update-project-set...

   • Edit

5. 5 Posted by Pure Krome on 30 Jan, 2015 03:25 AM

   

   Ta!

   Is there a GH issue re: yml per sln? (so i can subscribe to that)?

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 30 Jan, 2015 03:27 AM

   

   There is just a note here: https://github.com/appveyor/ci/issues/40

   but feel free to create a new dedicated item for that.

   • Edit

7. 7 Posted by Pure Krome on 30 Jan, 2015 03:34 AM

   

   Sweet - ta.

   Created the GH Issue here.

   • Edit

8. Pure Krome closed this discussion on 30 Jan, 2015 03:34 AM.