TeamCity pre-tested commit functionality

Hi Everyone,

We are currently evaluating TeamCity in a continuous integration scenario with SVN VCS.

The feature we find quite interesting is the pre-tested commit, but there are several limitations in the context of development process as I see it.

So I have two questions regarding this feature, perhaps someone with more experience in TC than myself can answer:

1. Is that possible to disable forcing the commit if the build has failed?
In certain projects we want to limit the commits to pre-tested commits only.

Of course my question is in the scope of TeamCity only, the VCS operations outside of TC will need to be managed separately.

2. Is there any API available for the client functionality?
For example trigerring a pre-tested commit from the API/command-line?

Thank you,

Michael.

1 comment

Michael,

> 1. Is that possible to disable forcing the commit if the build has failed?

A pre-tested commit is initiated via TeamCity IDE plugin and there is no way to prohibit developer to use VCS client to commit directly into the version control.
This can only be done on SVN commit hook-level. You can vote for the feature request that would make writing such commit hook a trivial task.

> 2. Is there any API available for the client functionality?

There is a command-line tool for submitting remote runs and it is open-source. However, the featue is not that simple and I am not sure you would want to use API for initiating remote runs.

Can you describe why do you need an API?

0

Please sign in to leave a comment.