Description of problem: Created a new EAP application, made change and verified. Then clicked 'Enable Jenkins Builds'. Jenkins master was successfully created as was the Jenkins job. However, making another change in the application led to the following failure: mhicks@dhcp-185-24 eapdemo$ git push Counting objects: 11, done. Delta compression using up to 4 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (6/6), 445 bytes, done. Total 6 (delta 4), reused 0 (delta 0) remote: restart_on_add=false remote: Executing Jenkins build. remote: remote: You can track your build at https://jenkins-cloudydemo.rhcloud.com/job/eapdemo-build remote: remote: Waiting for build to schedule............................................../opt/rh/ruby193/root/usr/share/ruby/json/common.rb:155:in `parse': 757: unexpected token at '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> (JSON::ParserError) remote: <html><head> remote: <title>502 Proxy Error</title> remote: </head><body> remote: <h1>Proxy Error</h1> remote: <p>The proxy server received an invalid remote: response from an upstream server.<br /> remote: The proxy server could not handle the request <em><a href="/job/eapdemo-build/api/json">GET /job/eapdemo-build/api/json</a></em>.<p> remote: Reason: <strong>Error reading from remote server</strong></p></p> remote: <hr> remote: <address>Apache/2.2.15 (Red Hat) Server at jenkins-cloudydemo.rhcloud.com Port 443</address> remote: </body></html>' remote: from /opt/rh/ruby193/root/usr/share/ruby/json/common.rb:155:in `parse' remote: from /usr/libexec/openshift/cartridges/abstract/info/bin/jenkins_build:24:in `get_jobs_info' remote: from /usr/libexec/openshift/cartridges/abstract/info/bin/jenkins_build:38:in `get_build_num' remote: from /usr/libexec/openshift/cartridges/abstract/info/bin/jenkins_build:75:in `<main>' 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: !!!!!!!! To ssh://94af85cf61cc4e28b95bfad484a218bd.com/~/git/eapdemo.git/ b39d16f..9e66183 master -> master mhicks@dhcp-185-24 eapdemo$ Version-Release number of selected component (if applicable): Tested against online on 2/1/2013 Actual results: Proxy error passed to the client and an error that the deployment was halted. The deployment WAS NOT halted and the application was successfully deployed. Expected results: The polling logic waiting for the build to schedule is not affected by interim failures and they are not passed to the client. If the client is told the deployment is halted, it should actually be halted. Additional info:
After bug 912215 is verified,we will verify this bug.
Counting objects: 3, done. Delta compression using up to 8 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (2/2), 242 bytes, done. Total 2 (delta 1), reused 0 (delta 0) remote: restart_on_add=false remote: Executing Jenkins build. remote: remote: You can track your build at https://jenkins-bmeng.dev.rhcloud.com/job/jbeap2-build remote: remote: Waiting for build to schedule...............................................................................Done remote: Waiting for job to complete...............................................................................................................................Done remote: SUCCESS remote: New build has been deployed. To ssh://5134828fa5944ea008000058.rhcloud.com/~/git/jbeap2.git/ ff08306..20b15b4 master -> master Checked on devenv_2890, does not meet the issue above. Move to Verified.