It's something strange and looks like a bug to me.
这是一件很奇怪的事，对我来说就像虫子一样。
A week ago I've created a Play! Framework 2 app with cloudbees ClickStart. Everything was working fine, was rebuilding from GitHub fine, was deploying fine.
一周前，我创造了一个剧本!框架2应用cloudbees ClickStart。一切都很顺利，从GitHub上重建，部署良好。
The crucial thing is that in the build configuration of this one week old app post-build part looks like this:
关键的一点是，在这个一周的构建配置中，构建后的应用程序是这样的:
The app I've created today with cloudbees ClickStart has different post-build part:
我今天用cloudbees ClickStart创建的应用程序有不同的后构建部分:
For some reason (Jenkins) has disappeared from Credentials and Account drop-down is empty.
由于某种原因(Jenkins)已经从凭证中消失，帐户下拉是空的。
It builds app successfully but then shows an error:
它成功地构建了应用程序，但随后出现了一个错误:
com.cloudbees.plugins.deployer.exceptions.DeployException: Cannot find user null
at com.cloudbees.plugins.deployer.impl.run.RunEngineImpl.<init>(RunEngineImpl.java:75)
at com.cloudbees.plugins.deployer.impl.run.RunEngineImpl$FactoryImpl.build(RunEngineImpl.java:170)
at com.cloudbees.plugins.deployer.impl.run.RunEngineImpl$FactoryImpl.build(RunEngineImpl.java:161)
at com.cloudbees.plugins.deployer.DeployPublisher.perform(DeployPublisher.java:103)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:790)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:762)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:715)
at hudson.model.Run.execute(Run.java:1617)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
Is it a bug or a feature???
是bug还是特性???
2 个解决方案
#1
5
This issue is caused when you disable one of the CloudBees DEV@cloud plugins. Try to re-enable or re-install the CloudBees Credentials Plugin.
这个问题是当您禁用一个CloudBees DEV@cloud插件时引起的。尝试重新启用或重新安装CloudBees凭证插件。
Update (2014-01-08)
A newer root cause is applicable if your Jenkins instance was hibernated or restarted any time after mid-November 2013. For these cases:
如果您的Jenkins实例在2013年11月中旬之后被休眠或重新启动，则可以使用更新的根原因。这些情况:
The update of DEV@cloud to the cloudbees-folder plugin version 4.0 (which only kicks in when your Jenkins instance is restarted after Nov 13th 2013) requires that the credentials plugin be upgraded to the latest (at least 1.9.3) and the ssh-credentials and ssh-slaves plugins be upgraded to the latest versions and Jenkins restarted.
DEV@cloud cloudbees-folder插件版本4.0的更新(只在詹金斯实例启动的时候启动后2013年11月13日)要求凭证插件升级到最新的(至少1.9.3)和ssh-credentials ssh-slaves插件升级到最新版本和詹金斯重启。
#2
0
I got exactly the same problem. After deleting a post-build action (i.e. Publish JUnit test results report) from the project's configuration the Jenkins option disappeared from the Credentials drop down. I updated Credentials Plugin from 1.7.6 to 1.9.4, restarted Jenkins, and it works again!
我也有同样的问题。从项目的配置中删除后构建操作(即发布JUnit测试结果报告)之后，Jenkins选项就从凭证上消失了。我更新了从1.7.6到1.9.4的凭证插件，重新启动了Jenkins，它又开始工作了!
