I need a way to specify which YML file to use.
As applications move to new environments, for example, from dev to production, I will need different build and deployment needs from environment to environment. Currently, my team prefers to use the appveyor.yml file to drive build configuration. But that yml file only works for one environment. For a production build, I am forced to use the GUI config tool and ignore the YML file. It would be great if I could specify in the GUI which YML file to use, if not the default "appveyor.yml". That way, I can have a versioned config for any environment I need.
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 05 Sep, 2014 07:30 PM
You can have separate YML configs per branch and you could have branch per environment. Let me know if I don't get the problem though.
2 Posted by sebastian on 02 Feb, 2015 07:44 AM
We use git flow in our workflow for release management and have our feature branches merge into develop branch, into release, then master etc. We, like byron, also have different requirements for our test, staging and production environments and it seems like we'd need different appveyor.yml files for each to achieve them.
Am I missing the 'appveyor' approach to this? Is there a way to setup different build pipelines in yml files neatly?
3 Posted by sebastian on 02 Feb, 2015 08:20 AM
I've just read this question and found it relevant and very useful:
http://help.appveyor.com/discussions/suggestions/232-conditional-build-confirguration
4 Posted by Pure Krome on 28 Feb, 2015 11:22 AM
@Sebastian and @bryon - see this thread: https://github.com/appveyor/ci/issues/129
5 Posted by sebastian on 01 Mar, 2015 03:21 PM
Thanks for the heads up!
I was going to target multiple builds in a single appveyor.yaml file by
branch, but this is a much more succint solution!
*Sebastian Nemeth*
*P: *0412 995 525
*E: *[email blocked]
*Semi Da Vinci*
Semi Inspired I.T. Solutions
Support Staff 6 Posted by Feodor Fitsner on 08 Mar, 2015 06:15 PM
It's been implemented and update deployed. There is a field on General tab of project settings for custom YML file name.
7 Posted by byron on 08 Mar, 2015 07:09 PM
This is awesome!!
--
Byron Sommardahl
CTO, Co-Owner
Acklen Avenue | www.acklenavenue.com | 615-669-8239
230 4th Ave N Suite 301H Nashville, TN 37219
Acklen Avenue is a custom software development company committed to
creating quality software that people love to use.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:54 AM.