Started on Aug 25, 2015 3:01:00 AM
Using strategy: Default
[poll] Last Built Revision: Revision 1fb0c00f548e2581ff32e879d284eb349ad5b226 (refs/remotes/origin/master)
ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@13413aa9[openHAB]
update: i received a response from the Cloudbees-Support which states that the problem should be solved now. Rootcause was most likely the update of their Dev@Cloud platform which caused a plugin incompatibility and we didn’t update the plugin accordingly.
Yep, switched to OH2 permanently yesterday, was just waiting for the latest build of the MiLight binding to occur with the whiteMode pull request merged.
Very happy with OH2 now i’ve fixed/worked around all the niggles. Good work
[ERROR] ExitStatusException occurred while running workflow: Java returned: 137
Exit codes above 128 mean that the java process was terminated via a signal, in this case it was 9 / SIGKILL (128 + 9 = 137).
Possibly killed by Jenkins because it took too long, or consumed too much RAM?
yes, i am still on it and didn’t create a ticket (yet). I just want to reach out to them with a qualified issue report. I started a build yesterday (before going to sleep) which unfortunately didn’t succeed either. Meanwhile one could use the builds from the CI server.
I’ve send a request to the Cloudbees Support who’s answered a minute ago:
You’re using small slaves, but the “small” slaves have only 1G memory, but your build is using a lot more, so our OOM killer stops your build. Please try using “standard” or “hi-speed” slaves instead of smalls.
@kai, we’re over quota so probably Cloudbees will refuse the next build.
Mind spending another update ?
Your total DEV@Cloud disk usage is over your subscription's quota. Your subscription 'foss-free' allows 10 GB, but you are using 11032 MB across all services (Forge and Jenkins). To fix this, you can either upgrade your subscription or delete some data in your Forge repositories, Jenkins workspaces or build artifacts.