Scheduled builds optionally use different yml file
TLDR: Allow scheduled builds to use a different appveyor.yml.
I was looking into setting up coverity and one of the suggestions was to use a scheduled build to work around the frequency limits. While I certainly could modify my appveyor.yml file, the modifications are ugly. Secondly, for a coverity build I won't be producing artifacts, running tests, or sending to Sonar. Basically the majority og my yml file. It would be great if scheduled builds could use a different yml. That was I could just have a simple build\run coverity yml.
Cheers,
Mike
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
1 Posted by Ilya Finkelshte... on 29 Nov, 2016 06:45 AM
Hi Mike,
Why not create second AppVeyot project targeting the same repo and tune it to use different YAML file? It is in Settings > General > Custom configuration .yml file name.
--ilya.
2 Posted by mike on 29 Nov, 2016 02:03 PM
That's brilliant! Sorry for the silly question. I'm new here:-)
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:09 AM.