Hi, I use jenkins and slack and have jenkins correctly sending builds to slack (non-pipeline, traditional project).
But sometimes we go for very long times between builds. So I would like the best practice, with the least alteration (or no alteration) to my jenkins server. So far I have seen a python program requiring pip and python library slacker and base64, etc. which changes the server too much. There is also the groovy/build-pipeline business of slackSend but that's pipeline. As everything in jenkins slack plugin is project/build oriented, I see no "send a slack message every hour to a given channel", to ensure that there is connectivity. Anyone know if there is something other than the above approach? Thanks. --Stuart -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/adf6d3e4-bf1b-4b57-a030-16e3c457e0aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
