on 20 Feb, 2020 06:03 PM
Well anyway... If "Default branch" can be configured only with UI and "It is possible to have both appveyor.yml and any of those UI setting" why "Branches to build" can not be overrided by appveyor.yml?
"Default branch" configured on UI is effective when you start a new build from UI with "New build" button and when a scheduled build is started. Branch filtering could only be done in either UI or appveyor.yml. If appveyor.yml exists all UI settings except environment variables and notifications are ignored.
on 20 Feb, 2020 07:39 PM
"If appveyor.yml exists all UI settings except environment variables and notifications are ignored."
This is wrong IMHO. Because of I need to exclude branch building in branch code and not in project configuration...So I need to put exclude in all branches except one that I want to build (and there I will pt "only": ).
Is it not logical?
on 20 Feb, 2020 07:48 PM
Let me describe this in more details.
We already have a lot of branches (like feature/something, etc).
So if we want to stop building some particular branch for some project (that should build master and all feature branches and etc) we need to make changes into appveyor.yml for that branch?
I think this should be done on project level.
My suggestion is to review this logic.