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

Global settings ignored after updating #22

Open
mikenikles opened this issue Apr 6, 2012 · 2 comments
Open

Global settings ignored after updating #22

mikenikles opened this issue Apr 6, 2012 · 2 comments

Comments

@mikenikles
Copy link

Hi,

Thanks for your work on that plugin, we've been using it for a while and are very satisfied. We encountered one issue that could possibly be addressed in a future version.

We configured our "Global HipChat Notifier Settings", then created our jobs and everything works well. However, once the jobs have been created, we changed the "Room". All jobs that we had created before making that change still point to the old "Room" value.

We can overwrite the "Room" property in every job and specify a "Project Room", but that's not very convenient.

Thanks,

Mike

@hajoeichler
Copy link

Hi,

this also happens for the HipChat authToken.
I had a quick look into the config.xml of one job and for the room I found even 2 entries:

... Foo false ... lalala://here.we.go 1234567890 Foo ...

As "jenkinsUrl" and "authToken" are global parameters in Jenkins they should not be stored on a per job basis.

@jstangroome
Copy link

Just discovered this the hard way too. Fixed it with:

find jenkins/jobs -name config.xml -print0 -exec sed -i 's,http://old,http://new,g' {} \;

Would be better if the plugin did not require this.

Palmr pushed a commit to Palmr/jenkins-hipchat-plugin that referenced this issue May 26, 2015
Add a 10 second timeout to HTTPClient
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

3 participants