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

Missing working example #40

Open
cojack opened this issue Dec 16, 2018 · 5 comments
Open

Missing working example #40

cojack opened this issue Dec 16, 2018 · 5 comments

Comments

@cojack
Copy link

cojack commented Dec 16, 2018

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:

  1. What's Telegram Bot name it's a username of bot with @ or without @? Or maybe it's display name but with suffix bot or without?
  2. /sub command at telegram boot chat doesn't return anyhing
  3. manual approval doesn't display any user after /sub
  4. messages are not publish by bot

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.

@Vintic
Copy link

Vintic commented Jan 3, 2019

try to install precedent version 1.2.1
Works for me.

@abdohossam5
Copy link

Even after installing 1.2.1. This plugin really needs a better documentation.

@machadodev
Copy link

machadodev commented Jun 13, 2019

Hey @cojack, how are you?

I had exactly the same problem.

I solved my problem clicking in:
"Manage Jenkins" -> "Reload Configuration form Disk"
and restarting Jenkins.

After that, Go again in telegram, click "Start" and "/sub".

This is how I sent a message e it worked:

Screenshot from 2019-06-13 17-06-13

Hope it helps. :)

@mxkyb
Copy link

mxkyb commented Jun 24, 2019

for me manual approval still is not working. the approval list in Jenkins settings stays empty.

[edit]
I tried reloading the settings and restarting Jenkins multiple times. also multiple tries with /sub command.

can you maybe post an example, how the configuration xml file should look? then I could approve it inside of the file.

[edit 2]
what worked for me in the end:

  • install plugin
  • restart jenkins
  • create telegram bot with botfather
  • add token and bot name (without the @) to Jenkins settings page
  • set mode to accept all
  • maybe reboot jenkins
  • send /start and /sub commands to the bot (in telegram)
  • set mode to manual accept
  • trigger your pipeline to test, it should work now

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.

@4n70w4
Copy link

4n70w4 commented Jan 25, 2021

Actual!

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

No branches or pull requests

6 participants