Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Ability to specify different custom messages for build success and build failure #212

Closed
r0bbie opened this issue Apr 19, 2016 · 9 comments · Fixed by #445

Comments

@r0bbie
Copy link

r0bbie commented Apr 19, 2016

This would be a really helpful feature.

Example use case:
We want to have a custom message to output a link to download the produced build on S3, only if the build was successful.

@r0bbie r0bbie changed the title Ability to specify different custom messages for build success and build failure Feature request: Ability to specify different custom messages for build success and build failure Apr 19, 2016
@samrocketman
Copy link
Member

I believe when #41 is resolved you should have this flexibility.

@rekahsoft
Copy link

I'm running version 2.01 of the slack-plugin for jenkins and this seems to not work. I am using the flexible-publishing plugin to deploy particular branches to the appropriate place. I'd like to display a message to my ci channel in slack saying "deployed $GIT_COMMIT to http://server.org" for one of the branches (which I check with the flexible-publishing plugin) and "deployed $GIT_COMMIT to http://server-staging.org" for the other. However the slack plugin options for both flexible-publish conditional action are always the same as the first conditional action that uses the slack-plugin.

@rekahsoft
Copy link

If you can point to where abouts I would need to make modifications I'd be happy to help out to rectify this issue :)

@samrocketman
Copy link
Member

If I knew I would patch it right away. It takes someone to debug and develop the solution. I appreciate your enthusiasm.

@csogilvie
Copy link

I believe this could be fixed by #169 ?

@samrocketman
Copy link
Member

@csogilvie Does #169 also address #41?

@csogilvie
Copy link

@samrocketman No, I suspect it probably doesn't.

@samrocketman
Copy link
Member

Though I think your change does resolve this issue.

@agentgt
Copy link

agentgt commented Jun 16, 2016

I may fork this project and try to see if I can do what Email-Ext does with Jelly scripts. Sadly this new Jelly script support I think is Jenkins 2.9 (I think).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants