Run personal build for existing changeset?

[6.0.3]

Hi,

Can I somehow start a personal build based on an existing changeset? My problem is we have TeamCity set up for building on commit, but sometimes when devs commit nearly at same time only 1 build with both changes is triggered (can that be avoided somhow?).

Can I somehow start a personal build or similar based on an existing changeset/revision? (I.e. so if I had the lowest changeset number in case above, I can start a build only with my changes).

Thanks.

4 comments
Comment actions Permalink

The only way I've found to avoid multiple changesets being included in a build is to turn off the VCS quiet period and make the VCS check period very small?

Regarding the personal build, I'd say that if you were worried about a check-in at the same time, normally you'd use this to check your individual changeset before you commit it. Otherwise I imagine the way you'd do this would be to locally svn switch to the revision you want and run personal build of that? Never tried that though; seems an odd thing to want to do.

If you're both committing at the same time, don't you want to run the build with changes together so you can see if your code integrates nicely together anyway?

0
Comment actions Permalink

Ok. (We've already turned quiet period off but I guess default polling is set to 60sec or so).
The reason to build isolated is to se unit test stats for a specific commit (coverage added/ignored/removed tests).
But I guess I can go with TC's run local changes and pre-tested commit in those cases I'm really interested i isolated stats.
Thanks.

0
Comment actions Permalink

Ahh yes, fair point re: isolated code coverage type of stats. On our setup we don't get coverage stat changes for personal builds though - but possibly depends whether you're using TC's integrated stuff or a separate Cobertura (or similar) config - we're using integrated IDEA runner.

0
Comment actions Permalink

Hi
We have TW-6996 request for isolated builds for each commit, please vote.
Note that decreasing VCS check interval helps only if you have enough agents available. For example if I have 1 agent, and 3 parallel commits then only 2 builds are launched.

A history build over specific revision can be started using Run Custom Build dialog, or from Change Log page.

Michael

0

Please sign in to leave a comment.