Our little build server found its voice and started contributing to the teams banter. I may have used string concatenation instead of proper JSON classes to construct a payload, but it didn't matter. I probably hard coded a few more strings and URLs than I should have. I spared people the public humiliation of a failure (for now). Just the name of the build, and who did it. Let the rest of the team feel happy some bugs where fixed. Success! The messages started to trickle in. I read some examples, hacked up a custom notifier class, zipped it up with some meta data, and a plugin was born: TeamCity has a plugin API apparently - Java based, and slack supports incoming webhooks allowing to to post anything you'd like, so with a little bit of free time between tasks, I decided to give it a go. Sure, developers would get their own personal success and fail messages via email if they wished, but unless you told someone, know one else had a sense of activity unless they loved checking out the TeamCity dashboard. It's easy to forget the little Mac Mini is playing an important role. It could be a fun way to let everyone know progress was being made as the day went on. I liked the idea of automated posts arriving in the general channel as new betas went live. Slack has many cool integrations with other tools like bug trackers, Github, bitbucket and even some for CI servers like Travis, but none (yet) for our favourite, TeamCity. We've been using Slack lately as a replacement for Jabber and Mail for internal comms which don’t scale well, and its been awesome. We use it to automatically build and deploy new iOS & Android app betas both internally for testing and to externally to clients.
0 Comments
Leave a Reply. |