Plugin not showing under configuration -> source management after installation

jenkinsci / discord-notifier-plugin

A post-build plugin that sends the build status to a Discord channel.

https://plugins.jenkins.io/discord-notifier/

MIT License

50 stars 25 forks source link

Plugin not showing under configuration -> source management after installation #102

Open rgupta8888 opened 1 year ago

rgupta8888 commented 1 year ago

Jenkins and plugins versions report

Environment

```text Paste the output here ```

What Operating System are you using (both controller, and any agents involved in the problem)?

Windows

Reproduction steps

Install plugin restart jenkins Project -> configure -> source managment -> discord webhook must be displayed

Expected Results

Project -> configure -> source managment -> discord webhook must be displayed

Actual Results

Project -> configure -> source managment -> discord webhook is not displayed

Anything else?

No response

Harshil-Jani commented 1 year ago

Even I am facing same issue. Any workaround yet ?

sachasmart commented 1 year ago

Same here..?

zachduda commented 3 months ago

Also having this issue. Thought I was crazy

sachasmart commented 3 months ago

Not sure if this is still relevant (my comment was from a year ago so its a little foggy), but I believe I got it working in the end:

                            discordSend description: '[SUCCESS] Web Cache Invalidated (Cloudflare Purged)',
                                title: env.JOB_NAME,
                                footer: env.JOB_URL,
                                image: '',
                                result: 'SUCCESS',
                                scmWebUrl: '',
                                thumbnail: '',
                                webhookURL: 'https://discord.com/api/webhooks/...'

zachduda commented 3 months ago

Thank you for your help @sachasmart!

Honestly invalidating the CloudFlare and browser caches didn't even cross my mind! I tried doing that but it seems to still have the same results. It's no worry though, probably easier to add a listener that will call a cURL request to Discord :)