I'm going to let Winston talk about this in more detail, but I'm aware that Oracle is leveraging its experience in cloud platforms to bring an end-to-end development experience to the cloud, and also I'm aware that Hudson is at the center of this effort.
Developing Cloud Applications vs Developing in the Cloud. Oracle Developer Cloud Service (ODCS https://cloud.oracle.com/mycloud/f?p=service:developer_service:0), a PAS for end-to-end development experience in the cloud, is an example of Developing in the Cloud. Hudson-3.x is integrated in to this offering. However, Hudson-3.x plays an important role in developing ODCS, itself a Cloud Application. We use Hudson-3.x (in the ODCS itself) not only as a CI tool, but we use it to automate most of the testing (UI, performance, acceptance, integration). We are in the process of setting up Continuous Delivery for ODCS (every checkin keeps the product in release state) and eventually Continuous Deployment (to staging to facilitate nightly UI & performance testing). If the entire build pipeline is done correctly (unfortunately there is no cookie cutter solution), every checkin must result in a staged deployment with potential for production deployment, if a build is promoted with in Hudson-3.x.
Time flies like an arrow. Fruit flies like a banana. Steve flies like a tiny ad:
create, convert, edit or print DOC and DOCX in Java