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

New value for buildServerUrl does not take effect #3

Closed
nheinric opened this issue Feb 23, 2014 · 6 comments
Closed

New value for buildServerUrl does not take effect #3

nheinric opened this issue Feb 23, 2014 · 6 comments

Comments

@nheinric
Copy link

Jenkins: 1.549
Java: 1.7.0_51-b13
OS: OSX 10.7.5
Slack plugin: 1.2

Changing the buildServerUrl in my Jenkins config was not having any effect: all build notifications in Slack still referred to the URL that I entered when I first configured the plugin.

I realized that this is because, while jenkins.plugins.slack.SlackNotifier.xml was being updated properly, my job-specific config was not.

However, there is no field in the project configuration frontend to set the buildServerUrl parameter.

Removing and re-adding the "Slack Notifications" post-build action resolved the issue for me, in the end.

@postmechanical
Copy link

Experiencing the same issue with version 1.2 of the plugin. Thanks for the workaround @nheinric.

@sebastianhenneberg
Copy link

Same issue here, workaround solves the problem. Thanks @nheinric

@samrocketman
Copy link
Member

Might this be fixed by #19 perhaps?

@samrocketman
Copy link
Member

This has been fixed with #26. The fix will be available in the next release slack-1.7.

@Nakilon
Copy link

Nakilon commented Nov 19, 2015

Happening just now with

Jenkins ver. 1.627
and Slack Plugin v1.8

How do I force the change?

@samrocketman
Copy link
Member

According to the original workaround you would remove and re-add slack notifications to the individual jobs.

timja pushed a commit that referenced this issue Nov 28, 2018
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

5 participants