Last 7 days

• Dec 22, 2009

  r14 (Teamcity 5 compatibility (not yet completed)) committed by simon.ti...@gmail.com   -   Teamcity 5 compatibility (not yet completed)

  Teamcity 5 compatibility (not yet completed)
• Dec 22, 2009

  issue 3 (Patch for TeamCity 5.0 notifications) commented on by SmartMaxim   -   You're right, testNameResponsibilityEntry1 is the new value and should be used. TestNameResponsibilityEntry contains ordinary responsibility data (who is responsible, who assigned, when, with what comment, what's current state) and also the test name. The 'getTestName()' method returns the full name including package name; you can use other presentations if you like (e.g. 'getTestNameWithoutPrefix()').

  You're right, testNameResponsibilityEntry1 is the new value and should be used. TestNameResponsibilityEntry contains ordinary responsibility data (who is responsible, who assigned, when, with what comment, what's current state) and also the test name. The 'getTestName()' method returns the full name including package name; you can use other presentations if you like (e.g. 'getTestNameWithoutPrefix()').
• Dec 22, 2009

  issue 3 (Patch for TeamCity 5.0 notifications) Status changed by simon.ti...@gmail.com   -   If I compare your patch with the API docs I think the message should use testNameResponsibilityEntry1 instead of testNameResponsibilityEntry. Patch: public void notifyResponsibleAssigned(TestNameResponsibilityEntry testNameResponsibilityEntry, TestNameResponsibilityEntry testNameResponsibilityEntry1, SProject sProject, Set<SUser> sUsers) { doNotifications("You are assigned responsible for " + testNameResponsibilityEntry.getTestName().getTestName(), sUsers, RabbitEars.SAD); } API: First value = oldValue Second value = newValue http://javadoc.jetbrains.net/teamcity/openapi/current/jetbrains/buildServer/notification/Notificator.html Could you verify this? What would be an example content of testNameResponsibilityEntry? I have no running Teamcity 5 server to test this.

  Status: Started

  If I compare your patch with the API docs I think the message should use testNameResponsibilityEntry1 instead of testNameResponsibilityEntry. Patch: public void notifyResponsibleAssigned(TestNameResponsibilityEntry testNameResponsibilityEntry, TestNameResponsibilityEntry testNameResponsibilityEntry1, SProject sProject, Set<SUser> sUsers) { doNotifications("You are assigned responsible for " + testNameResponsibilityEntry.getTestName().getTestName(), sUsers, RabbitEars.SAD); } API: First value = oldValue Second value = newValue http://javadoc.jetbrains.net/teamcity/openapi/current/jetbrains/buildServer/notification/Notificator.html Could you verify this? What would be an example content of testNameResponsibilityEntry? I have no running Teamcity 5 server to test this.

  Status: Started
• Dec 21, 2009

  r13 (Release 0.3) committed by simon.ti...@gmail.com   -   Release 0.3

  Release 0.3
• Dec 21, 2009

  buildbunny-0.3.jar (buildbunny version 0.3 (compiled against Teamcity 3.1.2)) file uploaded by simon.ti...@gmail.com
• Dec 21, 2009

  issue 2 (Functional patch) Status changed by simon.ti...@gmail.com   -   Hello Rob, thanks for the patch and sorry for my late reaction. I missed the notifications. The patch is applied to trunk and I will release a new version. My problem is that I couldn't test it on our TeamCity installation and our Nabaztag is moved away. I you have the possibility to verify the changes it would be great. Cheers Simon (mail@simon-tiffert.de)

  Status: Fixed

  Hello Rob, thanks for the patch and sorry for my late reaction. I missed the notifications. The patch is applied to trunk and I will release a new version. My problem is that I couldn't test it on our TeamCity installation and our Nabaztag is moved away. I you have the possibility to verify the changes it would be great. Cheers Simon (mail@simon-tiffert.de)

  Status: Fixed
• Dec 21, 2009

  r12 (Integrated patch by Robert Moran (changed to random voice if...) committed by simon.ti...@gmail.com   -   Integrated patch by Robert Moran (changed to random voice if no voice is specified)

  Integrated patch by Robert Moran (changed to random voice if no voice is specified)
• Dec 21, 2009

  issue 1 (Patch to specify TTS voice) Status changed by simon.ti...@gmail.com   -   Patch is applied to trunk, sorry for the delay. The notification was missing.

  Status: Fixed

  Patch is applied to trunk, sorry for the delay. The notification was missing.

  Status: Fixed
• Dec 21, 2009

  r11 (Integrated patch by Daniel Wellman) committed by simon.ti...@gmail.com   -   Integrated patch by Daniel Wellman

  Integrated patch by Daniel Wellman
• Dec 21, 2009

  r10 (Second call for ears still fails in some situations - revert...) committed by simon.ti...@gmail.com   -   Second call for ears still fails in some situations - reverted

  Second call for ears still fails in some situations - reverted

Earlier this year

• Nov 13, 2009

  issue 3 (Patch for TeamCity 5.0 notifications) reported by SmartMaxim   -   In 5.0 the notifier interface has been changed. Please accept the patch to support new responsibility notifications.

  In 5.0 the notifier interface has been changed. Please accept the patch to support new responsibility notifications.
• Sep 03, 2009

  issue 2 (Functional patch) reported by robert.moran   -   Hi, we have been using your build bunny plugin for team city you have hosted on google. I have built it for team city 4.5 and added a few extra features. The patch file for the features below is attached and you are welcome to add it to the project. * Exposed all build messages to the user for customisation * Included a voice named "Random" which will pick a random english-speaking voice for each message * Added #PROJECT#, #USER# and #COMMENT# placeholders which can be used in the messages and are replaced with the project name, user or username of the last person to make a change and their commit comments Cheers, Rob

  Hi, we have been using your build bunny plugin for team city you have hosted on google. I have built it for team city 4.5 and added a few extra features. The patch file for the features below is attached and you are welcome to add it to the project. * Exposed all build messages to the user for customisation * Included a voice named "Random" which will pick a random english-speaking voice for each message * Added #PROJECT#, #USER# and #COMMENT# placeholders which can be used in the messages and are replaced with the project name, user or username of the last person to make a change and their commit comments Cheers, Rob
• Jun 03, 2009

  r9 (A second message is needed to lower the ears) committed by simon.ti...@gmail.com   -   A second message is needed to lower the ears

  A second message is needed to lower the ears
• Jun 03, 2009

  r8 (Calls commented out) committed by simon.ti...@gmail.com   -   Calls commented out

  Calls commented out
• Jun 03, 2009

  r7 (New version with ears and voice) committed by simon.ti...@gmail.com   -   New version with ears and voice

  New version with ears and voice
• Jun 02, 2009

  r6 (Converted to Maven project) committed by simon.ti...@gmail.com   -   Converted to Maven project

  Converted to Maven project
• Jun 02, 2009

  r5 (Added ear positions) committed by simon.ti...@gmail.com   -   Added ear positions

  Added ear positions
• Apr 18, 2009

  issue 1 (Patch to specify TTS voice) reported by etldan   -   This isn't a bug report - it's a feature request/patch. Thanks for developing the 'buildbunny' plugin for TeamCity, we use it all the time at work. I've patched it to allow us to specify the voice, since some of the default voices are at a lower audio fidelity and clarity. If the user doesn't specify the voice, no voice parameter is specified in the API request. I renamed the UI label for Nabaztag ID since I wasn't sure what field it was, and it looks like the Nabaztag API now uses the parameter name "serial number" to describe it. This was more of a cosmetic change than anything. Attached please find a diff generated by 'svn diff' for the patches in case you would like to try any of them out. Thanks, Dan

  This isn't a bug report - it's a feature request/patch. Thanks for developing the 'buildbunny' plugin for TeamCity, we use it all the time at work. I've patched it to allow us to specify the voice, since some of the default voices are at a lower audio fidelity and clarity. If the user doesn't specify the voice, no voice parameter is specified in the API request. I renamed the UI label for Nabaztag ID since I wasn't sure what field it was, and it looks like the Nabaztag API now uses the parameter name "serial number" to describe it. This was more of a cosmetic change than anything. Attached please find a diff generated by 'svn diff' for the patches in case you would like to try any of them out. Thanks, Dan