-
Notifications
You must be signed in to change notification settings - Fork 64
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
Missing working example #40
Comments
try to install precedent version 1.2.1 |
Even after installing 1.2.1. This plugin really needs a better documentation. |
Hey @cojack, how are you? I had exactly the same problem. I solved my problem clicking in: After that, Go again in telegram, click "Start" and "/sub". This is how I sent a message e it worked: Hope it helps. :) |
for me manual approval still is not working. the approval list in Jenkins settings stays empty. [edit] can you maybe post an example, how the configuration xml file should look? then I could approve it inside of the file. [edit 2]
It works, because in accept all mode, the subscriptions are added to the jenkinsci.plugins.telegrambot.TelegramBotGlobalConfiguration.xml file. then on change to manual subscription, the entries stay. btw.: this file is the place, where the telegram chat-id is stored. |
Actual! |
Hi,
I would like to use this plugin, but there is lack of example how this is suppose to work. I have spend few hours combine how this stuff can be configured together and Im still facing an issues that:
Telegram Bot name
it's a username of bot with @ or without @? Or maybe it's display name but with suffixbot
or without?There is so manny missing information that I can not make any progress of how to use it.
Please @nikitabelonogov describe it a bit better.
The text was updated successfully, but these errors were encountered: