More than just responsibility for failed builds..I would like a bug!

Hi all,

Firstly I apologise if this question has already been answered somewhere, I have googled, searched these forums and read the documentation but I can't see a way of doing what I want to do, so here goes....

Whilst I like having the ability to assign responsibility for a failed build, I really want to assign a specific bug fix from my JIRA installation, is this possible?

Cheers

Rich

7 comments

Rich,

There is no such feature so far. Feel free to file a request into our tracker.
We discussed such a feature internally but it seems as creating an issue on each build failure is an overkill. Do you really have such practice in your projects?

0

Yegor, I would just like the ability to see all open bugs against a build definition. In the early stages of our project we seem to have builds break for more than just one person's responsibility, and so it would be nice to do bugs raised and open to show what is keeping a build from successfully completing.   Cheers  Rich

0

Rich,

Can you please desribe in detail how you imagine the feature? e.g. for an example sequence of events would TeamCity should do, etc.

0

Perhaps I can respond on Rich's behalf... since I work in the same team.

We have sevearl build definitions that are running tests, from unit tests through to more fv style tests. These definitions are set as dependancies on deployment jobs etc. So we only refresh a deployment if all the tests are passing.

We have upwards of 300 tests in a given definition, and sometimes there are multiple failures. At those times I wish to be able to set a bug association to a failed test, and have the top level build show all known bug associations. Ideally pulling a 'responsible' list from the owners of those JIRA bugs.

So yes we have a bug per build break, because we use the builds at a hook to trigger test automation, at least up to a certain level of complexity. If we could assign and track bugs against the test failures and see that agregated at the top level it would save us a considerable amount of time in managing the state of these definitions and what work remains to resolve outstanding issues.


UPDATE: - one other thing I realised that I'd like is the ability to add comments to a build result. Specifically for situations where it failed, and we understand why, but it doesn't require a defect. eg maybe a server crashed and is now running again. it is useful to indicate to the whole team that the issues has been investigated and is understood

Sincerely

Daniel

0

Daniel,

Thank you for the comment.

Well, our current approach is to track failure-responsible assignments within TeamCity, using "responsibility" feature. You can assign responsibility in TeamCity for an entire build configuraiton failure or for individual tests.
While disconnected from the issue tracker, that seems to be self-contained and centralized in the single place - you can investigate the failure, view the committing users, assign responsible and view who is currently responsible right from TeamCity UI.

So far we do not plan to add features to create issues in the tracker on failures in TeamCity as the already present feature covers the need mostly.

As a side note, ability to comment a build in already in since TeamCity 5.0 or even earlier. Look under "Build Actions" on build result page.

0

Yegor,
thanks for the response, appologies for the slow turn around from me, I was expecting to receive an email if there was a reply but I didn't.

I guess for me the issue is that I want to be able to tell at a glance if all of the separate reasons for failures in a build have been understood and are being worked on.
There is no way to see (that I've found) a summary view of how many failures have resposibility set versus those that do not. Or any summary list of everyone that has responsibility for failures within a build definition. It is only possible to set one person as owner for the entire configuration.

So even if we use the comments of responsibility to link to what we actually care about, the JIRA issue, there is no good way to get at this information, and no way to set it in bulk sections. Eg I might want to claim responsibility for 25 tests under one 'responsibility' and another 14 for a separate one. Are there any plans to make these things easier to manage even if there are no plans to allow clear issue linking?

Thanks for the tip of build comment, I had not spotted that, and it does help. I wonder if I can add such a comment via the REST api? (I'll look into it but if you can point me in the right direction that would be great)

Thanks again for your response.


Sincerely,

Daniel

0

Daniel,

> I was expecting to receive an email if there was a reply but I didn't.

Usually this works OK in email is set up, but the forum software can glitch sometimes.

I assume you use a recent version of TeamCity...


> There is no way to see (that  I've found) a summary view of how many failures have resposibility set  versus those that do not.

Current Problems and Responsibilities tabs of a project are designed to serve these needs. They are project-wide, however. For a build configuration level, please vote for the feature request.

> It is only  possible to set one person as owner for the entire configuration.

You can also assign responsibles for individual tests.


> Are there any plans to make these things easier  to manage even if there are no plans to allow clear issue linking?

In 6.0 you can add a comment when assigning responsibility for several tests in single action. Do you need other abilities?

Anyway, our current approach is to enhance responsibility tracking inside TeamCity instead of delegating the tracking into issue tracker. If you need some features that are not yet available, feel free to post a feature request detiling the case and your original related needs.


> I wonder if I can add such a comment via the REST api?

Try posting the comment text to URL .../id:<internal_build_id>/comment

See general REST API description on
http://confluence.jetbrains.net/display/TW/REST+API+Plugin

0

Please sign in to leave a comment.