StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18838862
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-09-16T23:14:49.850
FavoriteCount
0
LastActivityDate
2015-12-15T13:57:11.860
LastEditDate
2015-12-15T13:57:11.860
LastEditorUserId
61714
OwnerUserId
61714
ParentId
14827093
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Update: This answer is only relevant to TeamCity v8 or older I have tried this myself but sadly I suspect it's not currently possible. The <a href="http://confluence.jetbrains.com/display/TCD7/Build+Dependencies+Setup#BuildDependenciesSetup-Reusingbuilds" rel="nofollow">Build Dependencies Setup</a> documentation supports this: <blockquote> When build A depends on build B, you can pass properties from build B to build A, i.e. properties can be passed only in the direction of build chain flow and not vice versa. </blockquote> The (generally sensible) reason I think its like this is because of the following: <ul> <li>The dependent build configuration could be a dependency of more than one other build configuration.</li> </ul> Think about it: If two parents want to pass their (differing) parameters to the dependent build, what do they get for the "last successful build"? Theoretically TeamCity could check if the properties for the last build match what was needed (rebuilding otherwise). But even then you would end up with an ugly build history of builds for all different environments. This really doesn't fit with the concept of build configurations. The best way to reuse the build configurations is to template them, and then create multiple projects setting properties at the project-level so they are available to all the contained build configurations. Ultimately the best advice may be to reconsider if you really need to use two build configurations for your project at all. Best-practice is to minimize the number of build configurations and build steps - put as much build logic into your own scripts as possible.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOverride parameter in snapshots dependencies in TeamCity
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSchneider
UserOwnerUserId
1. USSchneider
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POOverride parameter in snapshots dependencies in TeamCity
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.