Winston Prakash

Greenhorn
+ Follow
since Oct 22, 2013
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
5
In last 30 days
0
Total given
0
Likes
Total received
3
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Winston Prakash

You can use Join Plugin for this purpose. See more details here

http://wiki.hudson-ci.org/display/HUDSON/Join+Plugin
10 years ago
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.
10 years ago
To reply to the question related to "it also talks about developing plugins"...

We have two chapters in this book - "Basic Plugin Development" & "Advanced Plugin Development". We have covered several API and Extension Points and most of them exists for a long time in both products. You may find them relevant for developing plugins for both products. Having said that, the code bases has changed considerably over the years. So there is no guarantee.
10 years ago
I agree with James and Ed. Writing test cases and using code metrics tools to measure the test coverage is a a good recipe for a successful software life cycle management strategy. While practicing Continuous Integration (CI) running these unit tests and make sure build does not fail is an important principle (See http://www.martinfowler.com/articles/continuousIntegration.html). However, keeping the CI build with in 10 minutes is another important guideline. So, while writing unit tests, keep that in mind and write independent tests for online & offline (example tests involve database connection) consumption. These CI builds must be run in stages to achieve the 10 minutes guidelines. How to achieve this using Hudson-3.x is covered in our book.
10 years ago
Ed is absolutely right. This book is not merely a user guide for Hudson-3.x. As per the Technology Radar (http://www.thoughtworks.com/radar) published by ThoughtWorks, Automated deployment pipeline is in adoption stage. Continuous Integration, Test Driven Development & Continuous Delivery are the various stages of Automated deployment pipeline. In this book we have covered most (if not all) of the principles to effectively use Hudson-3.x for this purpose.
10 years ago
Hudson-3.x is primarily developed at Eclipse Foundation. Though the spirit of both products remain the same, Hudson-3.x is mainly geared towards Enterprise users who require stability. Hudson-3.x is developed independently and substantial amount of work has been gone in to the product to cleanup the libraries with clean license (http://wiki.eclipse.org/Hudson-ci/development/third_party_libraries/3.0.0). There are several new features introduced in Hudson-3.x (http://wiki.eclipse.org/Hudson-ci#New_Features). Stability and performance are the primary goal of Hudson-3.x (http://wiki.eclipse.org/Hudson-ci/features/Memory_Performance). With that in mind, Hudson-3.x is released quarterly for bug fixes, bi-yearly for feature releases and yearly for major incompatible releases. This is in contrast to the weekly release. Every release under goes rigorous QA testing to ensure smooth transition; again a requirement for enterprise users.
10 years ago