Trigger only Debug build, not Release

Phil Dye's Avatar

Phil Dye

06 Nov, 2014 12:14 PM

Just trialling things to see if I can switch from TeamCity, and have the following question.

We currently have two 'build configurations', Debug and Release, for each project, only the first of which uses a trigger on commit. We trigger the Release build on-demand.

Is there a way to replicate this behaviour? I can see how doing it from different branches would work, but (rightly or wrongly) we currently (generally) use a single branch. ie I'd like a deploy to only happen for the Release build on-demand.

Phil

  1. Support Staff 1 Posted by Feodor Fitsner on 06 Nov, 2014 10:25 PM

    Feodor Fitsner's Avatar

    Branches are definitely better as you are having the same build number for both debug and release builds.

    Another way is to setup two projects MyApp - debug and MyApp - release that could be treated as TC build configurations. For release project you just remove webhook from repo to disable building on push.

    Yet another way could be a single project, where you have some Release=true|false environment variable distinguishing build flows. By default, in your appveyor.yml you could have 'Release=falsedefined and then when you are releasing you setRelease=true` on UI - it will override the one defined in YML.

    Let me know if you have any questions.

  2. 2 Posted by Phil Dye on 11 Nov, 2014 08:51 AM

    Phil Dye's Avatar

    Thanks Feodor - moving to branches is the "right" thing to do, but will require a change (albeit for the better) to our workflow.

    Phil

  3. Phil Dye closed this discussion on 02 Feb, 2016 09:49 AM.

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