Hide Forgot
Description of problem: Given one cartridge created(e.g., myjbossews21), embed with jenkins-client and change something in local git repo and git push, found jenkins build failed remote: Executing Jenkins build. remote: remote: You can track your build at https://jenkins-chunchen.dev.rhcloud.com/job/myjbossews21-build remote: remote: ERROR - Couldn't schedule job remote: !!!!!!!! remote: Deployment Halted! remote: If the build failed before the deploy step, your previous remote: build is still running. Otherwise, your application may be remote: partially deployed or inaccessible. remote: Fix the build and try again. remote: !!!!!!!! remote: An error occurred executing 'gear postreceive' (exit code: 1) remote: Error message: Failed to execute: 'control post-receive' for /var/lib/openshift/52afb14d64dce09073000001/jenkins-client remote: remote: For more details about the problem, try running the command again with the '--trace' option. To ssh://52afb14d64dce09073000001.rhcloud.com/~/git/myjbossews21.git/ bbe37eb..4602993 master -> master jenkins/logs/jenkins.log: --------------------------------------------------------------- Started by user Jenkins System Builder Building remotely on myjbossews21bldr in workspace /var/lib/openshift/52afb2a564dce09073000050/app-root/runtime/repo Checkout:repo / /var/lib/openshift/52afb2a564dce09073000050/app-root/runtime/repo - hudson.remoting.Channel@1e167e1:myjbossews21bldr Using strategy: Default hudson.util.IOException2: remote file operation failed: /var/lib/openshift/52afb2a564dce09073000050/app-root/runtime/repo at hudson.remoting.Channel@1e167e1:myjbossews21bldr at hudson.FilePath.act(FilePath.java:912) at hudson.FilePath.act(FilePath.java:889) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:968) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: java.io.IOException: Remote call on myjbossews21bldr failed at hudson.remoting.Channel.call(Channel.java:723) at hudson.FilePath.act(FilePath.java:905) ... 10 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer at hudson.FilePath.getChannel(FilePath.java:2387) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:976) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:968) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2444) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Archiving artifacts Finished: FAILURE Version-Release number of selected component (if applicable): INT(devenv_4141) devenv_4142 devenv_4143 How reproducible: always Steps to Reproduce: 1.create one cartridge and embed with jenkins-build #rhc app create myjbossews21 jbossews-2.0 --enable-jenkins 2.change something in local git repo and do git push #sed -i 's/Welcome to/Hi/g' src/main/webapp/index.html #git add -A &&git commit -amp&&git push 3. Actual results: Jenkins build failed when deploying Expected results: Jenkins build should succeed Additional info:
I think this is from our window when we had upgraded jenkins to 1.532 temporarily, which we figured out was broken and reverted it to 1.509. This should be working again now. We'll be updating to jenkins again in the near future once we get all the requisite changes in place.