We had Jenkins successfully deliver notifications to Flowdock, until we switched our job to the Build Flow Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin). Now we no longer get notifications, even though the "test connection" button successfully delivers a chat message to our Flowdock flow.

Ideas?

Would it be possible to define flowdock API-keys on a global level in flowdock? This would greatly aid when setting up and maintaining messages across many builds.

We have 40+ builds and 15-20 flowdock rooms spead across our teams. This would greatly aid whn "debugging" where messages are being sent by seeing "team board" instead of the API-key.

An alternative would be to have a UI on the global level where you could specify which builds post to flowdock, where and with which configuration

Given a commit with author foo <@>, the Flowdock plugin crashes when gathering author info for the message:

FATAL: 0
java.lang.ArrayIndexOutOfBoundsException: 0
    at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:291)
    at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:349)
    at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350)
    at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:672)
    at hudson.model.Run.execute(Run.java:1763)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)

We were wondering why the following wouldn't work, as only #jenkins appeared in tags.

So the tags literally have to be just comma-separated, like jenkins,develop,$Site. Not a big deal but looks like comma-and-space separated values are quite common in Jenkins, so I think it's easy to get this wrong.

When using a multi-configuration project the Flowdock plugin uses the projects label name for display instead of the actual project name.

Example:

• Project test-project has a multi-configuration setup with the label testing and two assigned nodes, one and two.
• After the build runs, Jenkins will report in the team inbox testing=one build X was successful and testing=two build X was successful.
• After a failed build, Jenkins will report in the flow testing=one build X failed.

I would expect messages in the style of:

• test-project build X on testing=one was succesful
• test-project build X on testing=one failed

Fixed notification is missing if there's aborted build between failed and success builds.
In eg.

When creating the list of commits for Flowdock messages, they commit messages might contain text that's considered a html tag. These get either converted to actual html or stripped when sanitizing, both of which are unwanted outcomes. The commit messages should be html escaped before being added to the Flowdock message.

I would like to be able for the nitfication to ping a team member when their build fails! :)

Because of https://github.com/jenkinsci/flowdock-plugin/blob/master/src/main/resources/com/flowdock/jenkins/FlowdockNotifier/config.jelly#L25 Flowdock notifier will by default notify when build is successful.

IMO, this is a bad idea both in term of general CI where you should consider success is the normal way, and only 'react' when something changes (say, fails). In the Flowdock specific case, like in emails btw, it results in flooding the flow inbox with "success" messages. And failure can easily go unseen.

Please change that behaviour. If you agree with the rationale above (i.e. reducing the noise), I can issue a PR very soon.

Thanks a lot

I thought it would work out of the box but it isn't. I have parametrised builds and the build name doesn't say everything about it so I'd like to tag it with the build parameters, but they aren't expanded in the messages. Would be nice to have it.

I have latest flowdock plugin and I tried to create a DSL with below combinations for this and I get error : java.lang.NoSuchMethodError: No such DSL method 'flowdock' found among steps
Example 1:
flowdock('flow-token') {
unstable()
success()
aborted()
failure()
fixed()
notBuilt()
}
Example 2:

publishers {
    flowdock('a-flow-token')
}

}

Hello,

Thank you for useful plugin. It will be really wonderful to be able to use it with pipelines

https://jenkins.io/blog/2016/05/25/update-plugin-for-pipeline/
https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md

Hi,
You mention in the Readme that I can clone, hack and release my own version of this plugin.
What I would like to achieve is to send the line in the job that states FAILURE: and the reason to the chat window.
Can you advise how I could do this please?

Regards
githubble

One of Flowdock's great features is the threads. It'd be natural and useful to get all messages for a particular build into the same thread.

I think it only requires some mapping of build to thread, if no thread exists, then a normal message is sent, its thread ID (which I'm assuming is returned by the Flowdock API) is stored, otherwise the thread ID found is used for the message.

At the moment it's possible to send messages to seperate flows, but not possible to specify which types of message go to which flow.

Also it's not possible to add mutiple Flowdock-steps, so I can't add seperate configs per flow.