StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POwhat part of the version number should be incremented on a continuous integration server
primarykey
Id
13222996
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-04T21:15:10.660
FavoriteCount
0
LastActivityDate
2012-11-05T09:06:14.547
LastEditDate
LastEditorUserId
0
OwnerUserId
373674
ParentId
0
PostTypeId
1
Score
2
ViewCount
396
LastEditorDisplayName
text
Body
I have integrated my solution in to a continuous integration tfsbuild 2010 server. This works nicely building all my libraries. Next I would like to increment the version number during each build on the CI server. The makeup of the version number is: (Major version).(Minor version).(Revision number).(Build number) My question is, what is the best practice as the number that should be incremented in this scenario? I would have thought the build number so that I end up with 1.1.1.123 and next check in results in 1.1.1.124 etc. What I am wondering though when does the revision number get incremented? Major is manual for major releases, the minor version as I create multiple branches for releases. Am I correct or what is the correct practice?
Tags
<continuous-integration><version><tfsbuild><version-numbering>
Title
what part of the version number should be incremented on a continuous integration server
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USamateur
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POwhat part of the version number should be incremented on a continuous integration server
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.