It turns out that the TestBean in the TeamCity API was removed, and I was using that to glean the test detail.  In version 0.8.24.121, I’ve worked around that by building my own bean and passing that to the template engine.

WARNING: This release is only compatible with TeamCity 6.5 and later. For Teamcity 6.0 and earlier, please use the earlier versions.

Screenshot: http://tcplugins.sourceforge.net/screenshot/tcPrettyEmail
Download: http://tcplugins.sourceforge.net/files/tcPrettyEmail
Documentation: http://sourceforge.net/apps/trac/tcplugins/wiki/TcPrettyEmail

If you find a bug or have feature request, please post a comment below or on the tcPrettyEmail bugs page.

With the recent release of Teamcity 6.5, some assumptions I was making about the prototype javascript functions proved incorrect. I think the newer version is stricter with badly named functions, or perhaps teamcity has changed some of their internal functions on which I was mistakenly relying.

This release fixes those bugs and also fixes a long standing oversight in the lack of checking of the URL and payload formats when submitting the form. Now, when trying to add a webhook with no url or no payload format selected you are prompted before the dialog goes away. Previously, the dialog would just close and no webhook would be added. It ended up being that my jsp was not setting the content type to text/xml, so the javascript error listener was never firing.

As usual, get the latest from sourceforge. If you find a bug please leave a comment below, or on the bugs page.

After some investigation, I noticed the the buildStatus does not get updated until after the build has been marked as “finished” by TeamCity. However, the build is not marked as finished until the plugins have run, so all builds were reporting themselves as “running”.

I have added a new field called buildResult, which gleans the result from the sRunningBuild object, rather than relying on the buildStatus returned by TeamCity.

Thanks to Lloyd for helping me work through the issues and testing. I have now uploaded a new 0.7.23.113 jar to sourceforge.

I also spotted that one field in the JSON payload was incorrectly stating that the notification was for buildStarted when in fact it was buildFinished. This has now been corrected.

In reality, it’s the same as the 0.22 xml format, so I’ve just changed the code to look for >= 0.22. This should work until the format changes again.

As usual, get the updated version from Gnome Look.

As always, get it from Gnome Look

The documentation has been added to the tcplugins wiki on sourceforge, and you can download the zipfile from source forge too.

Screenshot: http://tcplugins.sourceforge.net/screenshot/tcPrettyEmail
Download: http://tcplugins.sourceforge.net/files/tcPrettyEmail
Documentation: http://sourceforge.net/apps/trac/tcplugins/wiki/TcPrettyEmail

Fixes:
- Fix for newly created WebHooks not being persisted to plugin-settings.xml until re-edited.
- Plugin JSPs loaded using getPluginResourcesPath(), so plugin dir can be anything, and not hard-coded to “webhook”.
- webHookUrl form input style fix for linux (or large fonts in general). URL input field was too wide for div.

Features:
- WebHook blurb updated. A new link can be added to the “Further reading” section of the blurb by adding a <info> line to the <webhooks> section of the main-config.xml
- Enabled events are now listed in Tabs and Edit pages, eg. Build Started, Build Changed Status, Build Interrupted, Build Almost Completed, Build Responsibility Changed

Links:

More Info | Download | Install and usage docs

I welcome any and all feedback.

My TeamCity home  is /opt/TeamCity

Enable JSP development mode in Tomcat.

This setting alows you to hot delpoy JSPs, and Tomcat will re-compile them for you without a restart.  Edit <TeamCityHome>/conf/web.xml and find the JspServlet section. Change the development mode to true as per the section below.

<servlet-name>jsp</servlet-name>
   <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
     <init-param>
       <param-name>development</param-name>
       <param-value>true</param-value>
     </init-param>
  ...

Enable Java code hot-swapping with a debugger

We have enabled JSP hot-compile in the previous, now we need to configure Tomcat so that Eclipse can load new Java code into the JVM from within the Eclipse debugger.

For Linux, edit <TeamCityHome>/bin/teamcity-server.sh and insert the commands needed to start Tomcat with the debugger enabled. I added the TEAMCITY_DEBUG_OPTS variable, and then added it to the CATALINA_OPTS line.

TEAMCITY_DEBUG_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n"

 CATALINA_OPTS="$CATALINA_OPTS $TEAMCITY_SERVER_OPTS $TEAMCITY_DEBUG_OPTS -server $TEAMCITY_SERVER_MEM_OPTS -Dlog4j.configuration=file:$BIN/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djava.awt.headless=true"

For Windows, edit <TeamCityHome>\conf\teamcity-server.bat and insert the debug commands. I added the TEAMCITY_DEBUG_OPTS variable, and then added it to the CATALINA_OPTS line.

:server_mem_opts_done
SET TEAMCITY_DEBUG_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
SET CATALINA_OPTS=%TEAMCITY_SERVER_OPTS% %TEAMCITY_DEBUG_OPTS% -server %TEAMCITY_SERVER_MEM_OPTS_ACTUAL% -Dlog4j.configuration=file:../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/

Start Tomcat

Stop Tomcat if it’s running and then start it by running <TeamCityHome>/bin/teamcity-server.sh start (or <TeamCityHome>\bin\teamcity-server.bat start on Windows).

Have a look in <TeamCityHome>/logs/catalina.out  There should be a line similar to the one below indicating that Tomcat is running with the debug port open.

Listening for transport dt_socket at address: 8000

Configure Eclipse

In Eclipse, create a new Debug Configuration (In the Java perspective, it’s under the Run menu).

Find Remote Java Application, and click the new button.  In the Connect tab, set:

• Connection Type: Standard Socket (Attach)
• Connection Properties:
  • Host: localhost (assuming your TeamCity instance is on your local machine)
  • Port: 8000

In the Source tab, I added my Java source directory.

Connect to Tomcat in Eclipse

Run the new Debug Config, and change to the Debug perspective. A quote from the TeamCity dev page is relevant here.

if you do not change code affecting plugin initialization and change only body of the methods, you can attach to the server process with a debugger and hot-swap the code

So if you change your registers or constructors, you need to restart Tomcat.

Deploy your JSPs

When TeamCity starts, it copies the JSPs from your plugin into <TeamCityHome>/webapps/ROOT/plugins/<YourPluginName>/

Therefore, you can copy updated JSPs to here. This might be best acheived with a simple ANT script.

WebHooks are configured on a project basis, and when events occur in the build process, a POST request is submitted to the URL. You can configure as many URLs as you like (within reason) and which events will trigger the request.

There is support for proxies in this version, and webhooks are configured in the TeamCity UI. There are a few outstanding items to tidy up, but the core functionality is working.

The project is on SourceForge at tcplugins.sourceforge.net.

In MythStatusScreenlet 0.1.1, I’ve extended (subclassed) the Screenlets utils.ini_reader to load extra options for the theme. These options control the layout and style of all the elements of the MythStatusScreenlet. As a proof of concept, I’ve quickly built a few other themes including “mythbuntu” and “glass”. I’ve renamed the default mepo theme to mepo-transparent, and created a new one for mepo that has a black background. This is because of a comment on the download page saying that a user sometimes found it hard to see the screenlet when backgrounds were changed.

Additionally, there is now support for GTK popups using the Screenlets Notifier class. The MythStatusScreenlet will popup a Notifier window when MythTV starts or finishes a recording.

I’ve tried to add mouseover tooltips too. However, I’ve found it to be quite unreliable, so it’s turned off by default.

I recently built a new MythTV machine. I installed mythbuntu 8.04 on it, which installed MythTv 0.21  Since then, my myth box no longer presents the Temperature information. I suspect a few other people might have the same problem (based on a comment on the gnome-look site), so I’ve fixed the code to only try and display the Temperature information if it is present. However, this means that I can’t easily test the Temperature display when building the themes. Please post a comment if you have this working, or have problems with it. Does anyone know if Temperature info is no longer presented in Myth 0.21, or is it a MythBuntu thing?

As usual, downloads are at gnome-look.