Adding 'For' node to share configuration between branches doesn't work

Pierre Oppein's Avatar

Pierre Oppein

22 Feb, 2018 06:17 PM


I'm trying to overwrite some config values for some branches as explained here :

I'm using the following simple configuration :

version: 2.0.0.{build}
configuration: Debug
  patch: true
  file: '**\SharedAssembly.*'
  assembly_version: '{version}'
  assembly_file_version: '{version}'
  assembly_informational_version: '{version}'
- cmd: nuget restore
  publish_wap_xcopy: true
  verbosity: minimal
test: off

      - develop
  configuration: Stage

My builds get triggered from commits on BitBucket. If i remove the 'for' section at the end of this config file, my builds are starting just fine.
If i however leave the 'for' section, then my commits won't even trigger a build ... Nothing happens in appveyor, it does not even complain that the file is not well formatted or whatever, it just does not start any build.

Any clue ?

  1. Support Staff 1 Posted by Ilya Finkelshte... on 23 Feb, 2018 07:20 PM

    Ilya Finkelshteyn's Avatar

    Probably commit is not in the develop branch... If you could send us a commit ID and specific time BitBucket webhook was sent, we can check our traces to see the exact reason.

  2. Support Staff 2 Posted by Ilya Finkelshte... on 24 Feb, 2018 04:32 AM

    Ilya Finkelshteyn's Avatar

    Sorry, this is actually a bug. Please watch, should be fixed soon. For now as a workaround, please add empty for node like this (after existing one)

          - develop

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? 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