Put git branch name in message?

[tecnobrat]

Any way to put the git branch name into the message sent to hipchat?

[rbroemeling]

I just wanted to add in that we would also find this advantageous. Current messages look like:

[project] - #7 Success after 51 min (Open)

... it would be great if they could be changed to look like:

[project]/[branch] - #7 Success after 51 min (Open)

I checked out the plugin code and the changes look fairly straightforward, however I couldn't figure out where to get the current branch name from the Hudson/Jenkins API, so that has put me at an impasse.

[rocketraman]

+1

[jmcclell]

It would be nice to be able to configure messages all-together, actually. Maybe some kind of message templating.

[Mange]

👍

[kmullin]

👍 as well.

[tyler-smith]

I also think this is a good thing.

[kmullin]

Ok, so I took a stab at this. I found two approaches:

1. Look at ChangeLogSet to see if entries, read commitId(Msg,Author) from last entry in changes
   changes: https://github.com/uservoice/jenkins-hipchat-plugin/compare/add_commit_hash
2. HACK: basically grep build log for specific string to match branch and SHA1 hash
   heavily relies on a very short buildLog (< 100 lines)
   also there are specific hard codings for us in there
   changes: https://github.com/uservoice/jenkins-hipchat-plugin/compare/uservoice_hacks

I also looked into trying to use hudson.scm.SCM, but I couldn't figure out how to expose SCM related info... maybe someone more knowledgeable could help solve that.

These changes were branched from hipchat-0.1.4 release because it was the only known working version that we'd already been using.

[kscaldef]

Yes, message templating similar to email notifications would be really useful. For our parameterized builds, it would be much more useful to be able to include some of the parameters in the notification.

[colszowka]

➕ 1️⃣

[marcins]

Vote for having a per-project message template too. My use case is that I have a project with a parameter that determines whether to deploy to staging or production and in HipChat there's no way to tell which kind of build was run.

[marcins]

If anyone wants to try the plugin with Mustache notification templates I have a snapshot HPI up in Dropbox:

https://dl.dropbox.com/u/5336861/hipchat.hpi

YMMV, disclaimer, etc, etc :-)

Also check the updated README

[marcins]

FYI - It appears that the git plugin sets an environment variable GIT_BRANCH based on which branch is being built, so with the Mustache template you can output {{build.environment.GIT_BRANCH}}.

[borkdude]

+1

[JustinAiken]

👍

[tokyowizard]

+1

[dennisbaskin]

+1