-
Notifications
You must be signed in to change notification settings - Fork 144
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
Plugin installation broke credentials used by other plugins #373
Comments
Hi @hostalp , I have a running Jenkins instance with the forementioned plugin but I can't see the credentials-configuration.xml file anywhere, even after forcibely configuring additional clusters. |
I'm not sure how it could be easily reproduced. Looking at the credentials-configuration.xml file creation time I can see that it was created some time after the OpenShift plugin installation. By looking at the jenkins log I don't see anything logged at that particular time, but there were definitely some builds running. So perhaps some build that made use of one of those credentials triggered that. I can only speculate. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten |
@hostalp This is over a year old and we have had releases since then. Can you please verify if this is still an issue for you? |
Hello,
after installing this plugin, several other plugins broke as they lost access to their configured credentials.
This includes SonarQube Scanner plugin that has a server authentication token configured in the Jenkins server config and Dependency-Track plugin that has an API key configured in the Jenkins server config as well.
EDIT: And it also affected SSH credentials managed by the SSH Agent plugin in each job config.
These 2 plugins can't now see their (long time ago) configured credentials and are now only able to be configured with 2 types of OpenShift plugin related credentials.
I found out that this plugin caused creation of the following file (it didn't exist before) which contains the 2 above menitioned openshift credential types in the filter settings so it appears to be related.
credentials-configuration.xml
After uninstalling the OpenShift Client plugin and deleting the credentials-configuration.xml file things went back to normal.
Jenkins 2.303.2
OpenShift Client plugin 1.0.35
Credentials plugin 2.6.1 https://plugins.jenkins.io/credentials/
SonarQube Scanner plugin 2.13.1 https://plugins.jenkins.io/sonar/
Dependency-Track plugin 4.0.0 https://plugins.jenkins.io/dependency-track/
SSH Agent plugin 1.23 https://plugins.jenkins.io/ssh-agent/
The text was updated successfully, but these errors were encountered: