Less code duplication in appveyor.yml when using branches.only?
Full appveyor.yml file
I have two very similar configurations (release/testing) which differ only by the range of platforms (testing does only x86 for speed), and also the "testing" configuration should not do deployment and artifacts.
I had to copy paste the existing YML twice, indent and add
configuration: stanzas.
Is there any better way to have a shared or "fall through"
configuration ? I still would like to have
a possibility to define a configuration that gets invoked when none
of the branches rules batch.
Something along those lines:
-
branches:
only:
- release
configuration: release
deploy: ....
continue: shared
-
configuration: testing
continue: shared
# no deploy
-
branches:
never
configuration: shared
Besides, list syntax of YAML is very unreadable
when used with the branches.only feature - I was
trying to get a syntax right only to notice I have to put a "-"
(minus) in the first column, and indent the rest.
Related: Two builds are launched on a tag
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac

Support Staff 1 Posted by Feodor Fitsner on 09 Sep, 2015 08:57 PM
Thanks for your suggestion!
Looks like the similar request: https://github.com/appveyor/ci/issues/325
2 Posted by saper on 09 Sep, 2015 10:21 PM
Closing this in favour of https://github.com/appveyor/ci/issues/325 and http://help.appveyor.com/discussions/suggestions/728-shared-setting..., thank you.
saper closed this discussion on 09 Sep, 2015 10:21 PM.