[JIRA] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Joseph Hughes created an issue Jenkins / JENKINS-50557 GCR Credentials Plugin does not work Issue Type: Bug Assignee: Wei Z Components: google-container-registry-auth-plugin Created: 2018-04-04 03:34 Environment: Jenkins ver. 2.109 Labels: docker Priority: Blocker Reporter: Joseph Hughes All builds trying to use this plugin result in the following... ERROR: Could not find credentials matching gcr:SOMEPROJECT hudson.AbortException: Could not find credentials matching gcr:plasma-column-128721 at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:217) at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:204) at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:196) at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:455) at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:431) at com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:373) at com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:311) at com.cloudbees.dockerpublish.DockerBuilder$Perform.access$100(DockerBuilder.java:291) at
[JIRA] [core] (JENKINS-24938) On restart Jenkins rewrites some config.xml values
Joseph Hughes created JENKINS-24938 On restart Jenkins rewrites some config.xml values Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Sep/14 4:37 PM Description: I have been seeing this behavior for a while now. I have a standard ubuntu installation using the official package. Every time I reboot the jenkins process to update a plugin of a version my Views and Slave Port configuration are overridden. For instance my original config.xml includes the following. views hudson.model.AllView owner class="hudson" reference="../../.."/ nameAll/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ /hudson.model.AllView listView owner class="hudson" reference="../../.."/ nameiOS/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ jobNames comparator class="hudson.util.CaseInsensitiveComparator"/ /jobNames jobFilters/ columns hudson.views.StatusColumn/ hudson.views.WeatherColumn/ hudson.views.JobColumn/ hudson.views.LastSuccessColumn/ hudson.views.LastFailureColumn/ hudson.views.LastDurationColumn/ hudson.views.BuildButtonColumn/ /columns includeRegex(?i).IOS-./includeRegex recursefalse/recurse /listView /views primaryViewAll/primaryView slaveAgentPort8098/slaveAgentPort After a restart that section of the config.xml is reduced to. views hudson.model.AllView owner class="hudson" reference="../../.."/ nameAll/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ /hudson.model.AllView /views primaryViewAll/primaryView slaveAgentPort0/slaveAgentPort I have watched the jenkins.log file closely and seen no errors or warnings in regard to why these two things specifically are being reset. What is also strange is that the rest of the core config is persisted and remains unchanged. Environment: Ubuntu 1.582 Project: Jenkins Labels: jenkins Priority: Major Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24938) On restart Jenkins rewrites some config.xml values
Joseph Hughes commented on JENKINS-24938 On restart Jenkins rewrites some config.xml values Also, when I make the changes through the UI then view the xml I see what I would expect to be there, but when I restart it is gone again. It does seem to be limited to just these two config values, Views and the Slave port. Everything else persists correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24938) On restart Jenkins rewrites some config.xml values
Joseph Hughes commented on JENKINS-24938 On restart Jenkins rewrites some config.xml values I am not manually modifying the config.xml while jenkins is running. I backed up the config before I did a restart so I could compare the two files. The result is what you see above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24938) On restart Jenkins rewrites some config.xml values
Joseph Hughes commented on JENKINS-24938 On restart Jenkins rewrites some config.xml values Security is enabled. I am using Jenkins user database along with the Role Strategy Plugin. https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin I do not see any init.groovy or a init.groovy.d folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24938) On restart Jenkins rewrites some config.xml values
Joseph Hughes commented on JENKINS-24938 On restart Jenkins rewrites some config.xml values It is not installed... but if it would be helpful I could install it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rbenv] (JENKINS-24633) Rbenv plugin sometimes does not release lock correctly
Joseph Hughes created JENKINS-24633 Rbenv plugin sometimes does not release lock correctly Issue Type: Bug Assignee: Unassigned Components: rbenv Created: 08/Sep/14 4:51 PM Description: In cases where a build throws an exception, a gem does not install correctly, or rbenv does not install correctly, or sometimes just randomly the .rbenv_lock file is left in the home directory of the build executer. To fix this issue the teardown mechanism should be used to ensure if a build created the lock, the build releases the lock for other projects to continue to use rbenv on the executer. Project: Jenkins Priority: Minor Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24297) Jobs DSL Plugin Master Branch tests failing
Joseph Hughes created JENKINS-24297 Jobs DSL Plugin Master Branch tests failing Issue Type: Bug Affects Versions: current Assignee: Daniel Spilker Components: job-dsl-plugin Created: 18/Aug/14 1:18 AM Description: Master Branch of the plugin currently failing tests due to this commit. https://github.com/jenkinsci/job-dsl-plugin/commit/f08528fce4ad14e950e9f6bcf9162632eb5ca6da Project: Jenkins Priority: Critical Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24297) Jobs DSL Plugin Master Branch tests failing
Joseph Hughes commented on JENKINS-24297 Jobs DSL Plugin Master Branch tests failing Seems like the build should be doing a clean before test. With a clean workspace I can get all the tests to pass. With a workspace that has been build with commit before the commit mentioned in this issue, the tests fail because the Message class is not generated from Message.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24146) rbenv support for job dsl plugin
Joseph Hughes created JENKINS-24146 rbenv support for job dsl plugin Issue Type: New Feature Affects Versions: current Assignee: Daniel Spilker Components: job-dsl-plugin Created: 07/Aug/14 1:01 AM Description: Currently there is only support for the rvm wrapper. I prefer the rbenv wrapper for my ruby builds. Project: Jenkins Priority: Major Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rbenv] (JENKINS-24002) Rbenv plugin fails to remove .rbenv.lock
Joseph Hughes created JENKINS-24002 Rbenv plugin fails to remove .rbenv.lock Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: rbenv Created: 28/Jul/14 2:52 PM Description: In some situations the following command is executed to remove .rbenv.lock bash -c "rmdir \$HOME/.rbenv.lock" This command fails if .rbenv.lock does not exist. I believe a more robust solution would be to use bash -c "rm -rf \$HOME/.rbenv.lock" which will remove the directory if it exists and carry on if it does not. Environment: Ubuntu 14.04 Project: Jenkins Labels: plugin Priority: Minor Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rbenv] (JENKINS-24002) Rbenv plugin fails to remove .rbenv.lock
Joseph Hughes commented on JENKINS-24002 Rbenv plugin fails to remove .rbenv.lock https://github.com/jenkinsci/rbenv-plugin/pull/29 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23259) userContent can been browsed by anoymous users when security is enabled and discovery is disabled
Joseph Hughes created JENKINS-23259 userContent can been browsed by anoymous users when security is enabled and discovery is disabled Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 30/May/14 8:09 PM Description: With security enabled and discovery disabled an unauthenticated user can browse any files in the userContent directory by going to http://server/userContent This can be a big security risk for those who use the copy_to_slave plugin and store sensitive files in the userContent directory. Environment: Ubuntu 14.04 Project: Jenkins Priority: Critical Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
