Deployment conditions fail on the empty string

withoutprecedence's Avatar

withoutprecedence

15 Sep, 2015 09:34 PM

I'm trying to push to NuGet when the build variable 'GitVersion_BuildMetaData' is the empty string. There seems to be a bug in the deployment condition check that fails for this.

See this line for an example: https://ci.appveyor.com/project/MortenChristiansen/overflow-net/build/1.0.0%20(Build%20107)#L163

  1. Support Staff 1 Posted by Feodor Fitsner on 15 Sep, 2015 11:49 PM

    Feodor Fitsner's Avatar

    Interesting. Will take a look.

  2. Support Staff 2 Posted by Feodor Fitsner on 18 Sep, 2015 07:08 PM

    Feodor Fitsner's Avatar

    Looks like when environment variable is empty means it's not defined at all.

  3. 3 Posted by withoutpreceden... on 20 Sep, 2015 07:08 PM

    withoutprecedence's Avatar

    Is this a behavior that will be changed or should I look for another way to determine when to publish my packages?

  4. Support Staff 4 Posted by Feodor Fitsner on 20 Sep, 2015 07:10 PM

    Feodor Fitsner's Avatar

    Yeah, it's fixed. Going to deploy update later today.

    - Feodor

  5. Support Staff 5 Posted by Feodor Fitsner on 21 Sep, 2015 03:46 AM

    Feodor Fitsner's Avatar

    Update has been deployed.

  6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:00 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