| Issue 16: | Should we host a CI Build at CloudBees | |
| 1 person starred this issue and may be notified of changes. | Back to list |
http://www.cloudbees.com/foss/foss-dev.cb Free, there is support for Gradle, though I hear it is currently a bit more complex (soon to be simplified in an upcoming release): https://cloudbees.zendesk.com/entries/20212337-add-gradle-plugin Though they have their own Git repositories, you are free to use your own according to their FAQ
Nov 22, 2011
Project Member
#1
kandpwel...@gmail.com
Labels:
Priority-Low
Nov 30, 2011
+1 on this! Sounds fun... I think some of the Gradle issues will be a prerequisite
Dec 2, 2011
Other potentials I found are: FaZend: http://www.fazend.com/ Code Better -- Team City: http://teamcity.codebetter.com/ but they both looked less mature than CloudBees
Dec 2, 2011
I just applied for a free FOSS account at CloudBees. It looks like they support Gradle and external repositories.
Dec 7, 2011
(No comment was entered for this change.)
Status:
Started
Dec 9, 2011
If this ever gets rolling, here is more info that seems to indicate that GoogleCode as an external repository is supported at CloudBees: http://web-static-cloudfront.s3.amazonaws.com/docs/supportedPlugins.pdf
Dec 9, 2011
latest update: registration completed. I can get you a login as well as myself. Having trouble tonight getting into the DEV@Cloud setup page, but that may be related to them transitioning to a new site (which is why my form submission was failing, they told me). Anyway, it looks like additional plugins beyond those listed in their core set may not be installed under the free-account terms, so no Googlecode plugin. But I think that just means less-tight googlecode integration; instead of autmoatic builds from checkins, we use a SCM-polling interval. I can't get any farther (further?) tonight.
Cc:
codeto...@gmail.com
Dec 10, 2011
OK, still sounds good. Let me know how I can help. A login sounds useful...
Dec 10, 2011
More help I found, for when CB resolves the issue I am still having with our subscription: http://blog.cloudbees.com/2011/11/polling-must-die-triggering-jenkins.html
Dec 12, 2011
CloudBees got us all registered for the services. I tried creating a build tonight, but I can't figure out how to provide any credentials to GoogleCode for Git. I posted a question at: https://cloudbees.zendesk.com/entries/20770552-try-to-integrate-googlecode-git-repository-into-foss-dev-cloud-jenkins-build I have disabled the sample build for now, as we have a limited amount of processor time per month, and I don't want it to keep polling while it's broken.
Dec 13, 2011
My experience with the website is much better now. It looks like the build worked, and the tests passed! This is really great.
Dec 13, 2011
I now have Jenkins configured to receive a post-commit trigger, and GoogleCode configured to supply the trigger, and it works (sorry for the several useless test checkins). I will try to tweak the commit URL to provide the revision number (later -- gotta sleep some time)
Dec 14, 2011
Removed the trigger and went back to 5 minute polling, because: "While we will make a best effort to promptly deliver all Post-Commit Web Hook notifications, messages are not guaranteed to be delivered, may arrive multiple times, and may not arrive in order of commit." Each commit was resulting in several builds, because we were getting multiple trigger POSTs at CloudBees for each commit. I could see it potentially chewing thru our allotted 2000 minutes of m1.small build time at CB.
Dec 14, 2011
I updated the bottom of our home page to include the required CloudBees logo (and some links), and I put an external link to our snapshot on the sidebar menu.
Dec 14, 2011
All very good stuff. Is the poll time configurable? I think it could be 60 or 120 minutes versus 5 minutes, no?
Dec 14, 2011
fully configurable, with CRON-like notation. I had it longer initially, but then it looks like the poll itself doesn't count against our build time if the poll finds nothing new to build. A side-note: I also noticed by watching the build console during several successive builds that it is Maven-retrieving the dependencies for *every* build. I have no clue whether or how we would want to alter it. Build-time is still only between 1-3 minutes currently. If we ever create a more elaborate build with several different JDK and/or codegen library versions, I would think we would want to make this more efficient if possible.
Dec 14, 2011
re: poll at 5 minutes. It just seems like a waste for a project of this size. re: retrieving. Interesting. My guess is that CB does not assign us space per se but rather runs the jobs dynamically on whatever server is available. If this is true, then none of Gradle, Maven, or Ant + Ivy will change that. My guess is that the download will dominate the time spent in the build. Anyway, definitely noted regarding keeping things efficient (in general).
Dec 16, 2011
We can continue to make tweaks to CloudBees CI, but I am calling this story done
Status:
Fixed
|