# Reset Build Counter Action

**URL:** <https://www.finalbuilder.com/forums/t/reset-build-counter-action/5014>\
**Category:** Discussion\
**Created:** [July 21, 2013, 9:33am UTC](https://www.finalbuilder.com/forums/t/reset-build-counter-action/5014 "2013-07-21T09:33:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![christian.leh](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/c/67e7ee/32.png) [@christian.leh](https://www.finalbuilder.com/forums/u/christian.leh)\
**Post date:** [July 21, 2013, 9:33am UTC](https://www.finalbuilder.com/forums/t/reset-build-counter-action/5014/1 "2013-07-21T09:33:50Z")

</div>

Currently you can reset the build number counter easily through stage details.

Would be nice to have that as action, so you would be able to start at 0 again, if any other part of the version number is changing.

e.g in trunk, we increase the version number when having schema changes to the database, for sure this will be a "new version" but its trunk and a nightly build of trunk should reflect that by robust version pattern like:

**Major.Minor.Schema.Counter**

So before the change, the 67th build of the current branch might have version number:

1.2.3.67 (where 67 is the counter variable from CI)

changing something in the branch that is causing the version number to change&nbsp;

1.2.4.68 (build number (.NET version pattern) changed from 3 to 4), the 68 for revision part would be wrong because it should be

1.2.4.0&nbsp;

so having a way to set the build counter using an action, this could be fixed.

What do you think about that (well, its already there but manually).

---

<div class="post-metadata">

**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\
**Post date:** [July 22, 2013, 12:06pm UTC](https://www.finalbuilder.com/forums/t/reset-build-counter-action/5014/2 "2013-07-22T12:06:01Z")

</div>

Yes, something like that is on our todo list. The idea is to have a bunch of different version schemes.   
  
 FWIW, I believe people over think versions somewhat, I prefer to keep it simple, I generally never reset the .net revision (or win32 build), ie the last part of the version number until the major version changes… there’s no need, the highest number is the latest build for that major version.

---

<div class="post-metadata">

**Author:** ![christian.leh](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/c/67e7ee/32.png) [@christian.leh](https://www.finalbuilder.com/forums/u/christian.leh)\
**Post date:** [July 22, 2013, 8:37am UTC](https://www.finalbuilder.com/forums/t/reset-build-counter-action/5014/3 "2013-07-22T08:37:25Z")

</div>

well, you cannot change a system that is shipped for over 10 years now. it works as it works i general, you are right. everything should be as simple as possbile.

---

<div class="post-metadata">

**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\
**Post date:** [July 22, 2013, 8:45am UTC](https://www.finalbuilder.com/forums/t/reset-build-counter-action/5014/4 "2013-07-22T08:45:54Z")

</div>

Fair enough. Hopefully it won’t be too long before we get to that feature work.
