Analysis updated 2026-07-10 · repo last pushed 2017-02-15
Keep a clean daily record of which builds completed and when.
Troubleshoot why certain builds finish unexpectedly by reviewing the event log.
Learn how to write a custom TeamCity plugin by studying the sample code.
| yaegor/teamcity-plugin-buildeventssample | asutosh936/job-finder-app | asutosh936/spring-boot | |
|---|---|---|---|
| Stars | — | 0 | — |
| Language | Java | Java | Java |
| Last pushed | 2017-02-15 | — | 2016-07-02 |
| Maintenance | Dormant | — | Dormant |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 2/5 | 2/5 | 3/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a running TeamCity server to install the plugin, plus Maven to build the zip package.
This is a sample plugin for TeamCity, which is software that development teams use to automatically build, test, and release code. The plugin's single job is to keep a record of when builds finish. It writes these events into a dedicated log file so that someone can easily look back and see exactly what happened and when. In practice, the plugin acts as a simple listener that watches the server's activity. Whenever a build completes, it captures that moment and writes it to a specific file called teamcity-buildEvents.log. To get it working, an administrator places the plugin into a special folder on the server, restarts, and then turns on a matching logging preset in the administration panel. After that, the custom log file appears and starts collecting data. This tool is really aimed at people who already manage a TeamCity server and want a straightforward way to track build completions without digging through the system's main, often noisy, logs. A development lead, for example, might use it to keep a clean record of daily build activity or to troubleshoot why certain processes might be finishing unexpectedly. Because it is described as a "sample," it is likely most useful as a learning resource for someone who wants to understand how to write their own TeamCity plugins. The project is written in Java and uses Maven, a common tool for organizing and packaging code. The build process produces a zip file that you drop into the server, which is a fairly standard approach for this kind of extension. The README is sparse on deeper technical details, keeping the explanation limited to the basic steps of building, installing, and reading the resulting logs.
A sample TeamCity plugin that logs every build completion event to a dedicated file, making it easy to track build history without searching through noisy system logs.
Mainly Java. The stack also includes Java, Maven, TeamCity.
Dormant — no commits in 2+ years (last push 2017-02-15).
No license information is provided in the repository, so usage terms are unclear.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.