get_build_number -- is always 0

11 views
Skip to first unread message

Alex McCool

unread,
Jun 11, 2015, 6:21:20 PM6/11/15
to chucknorri...@googlegroups.com
newbie here, first day of using uppercut

I now have my nupkg nuget package getting created, yay!    However I cant seem to find a way to get the version.build to increment.

my build log always has this:

            
     [echo] Using revision number: 0 and hash: d28fc890af398b73e1cf27d5ec4098d1f5b93a5c.

get_build_number:

     [echo] Using build number 0.


the project is in github

here is a snippet from uppercut.config file
  <!-- ASSEMBLY VARIABLES -->
  <property name="version.use_semanticversioning" value="true" overwrite="false" />
  <property name="version.major" value="0" overwrite="false" />
  <property name="version.minor" value="2" overwrite="false" />
  <property name="version.patch" value="1" overwrite="false" />
  <!--<property name="version.build" value="0" />
  <property name="version.revision" value="0" />-->

Rob Reynolds

unread,
Jun 11, 2015, 6:57:41 PM6/11/15
to chucknorri...@googlegroups.com
Build number is something that comes from Team City or Jenkins. What are you using for CI?

--
You received this message because you are subscribed to the Google Groups "chucknorris" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chucknorrisframe...@googlegroups.com.
To post to this group, send email to chucknorri...@googlegroups.com.
Visit this group at http://groups.google.com/group/chucknorrisframework.
For more options, visit https://groups.google.com/d/optout.



--

Rob Reynolds

unread,
Jun 11, 2015, 7:00:25 PM6/11/15
to chucknorri...@googlegroups.com
Since you switched it over to use SemVer, you should be seeing the patch version go into the build number spot. Are you not seeing that happen?

:)
Reply all
Reply to author
Forward
0 new messages