Notice: This resource is no longer being actively maintained and as a result some information may be out of date or inaccurate. Please see for technical instructions or for support related concerns.
CloudBees Toolkit for Eclipse How-to Guide

CloudBees Toolkit for Eclipse How-to Guide

Last modified by Harpreet Singh on 2013/07/10 02:31

This page is for v1.0. You are likely looking for the latest version 2.0 (link)

This article describes how to use the CloudBees Eclipse Toolkit plug-in to develop and deploy applications in the CloudBees platform. The article describes how to set up a SVN repository in the CloudBees forge, build on DEV@cloud and deploy the application on RUN@cloud through Eclipse.

Before installing the the eclipse toolkit plug-in, we recommend that you install the Subversive and Subclipse SVM plug-in from the Eclipse marketplace.

Step 1: Install the CloudBees Eclipse Toolkit Plug-in

The CloudBees Eclipse toolkit plug-in is found at

  • Go to help option under Eclipse and install the plug-in by putting in the URL.
  • Install all the plugins listed as shown in Image 1.
  • Once installed, restart eclipse to detect the plug-in and use it.


Image 1: Adding CloudBees Eclipse Toolkit Plugin

Step 2: Validate your CloudBees Account

Next up, is to validate your current CloudBees account information. You will need to enter your e-mail and password information that you used to create your CloudBees account. If you do not have an account – check the video here that shows you how to set one up.

Click the validate button - the toolkit sets up your information to match that on Enable the checkboxes for continuous integration access and forge repositories. Image 2 shows the validate account window.

Enable CloudBees’ perspective, to have the CloudBees related information show up on your IDE. Image 3 shows this perspective. On the bottom left window the  information about forge repositories, DEV@cloud and RUN@ cloud services shows up.


Image 2: Validating CloudBees account 


Image 3: CloudBees Perspective in Eclipse

Step 3: Create a new SVN repository on CloudBees

Go to your CloudBees account, click on “Repositories” and create a new SCM repository. Image 4, shows a newly created repository. We will be using the URL listed under “authenticated access” with the given username.

The UI allows you to delete repositories if you choose to do so.


Image 4: Create a new repository


Step 4: Create a new CloudBees project

Go to the CloudBees icon on the Eclipse toolbar, and click “New CloudBees Project…” information. Enter host repository information and new Jenkins job to select the appropriate Jenkins instance (the toolkit automatically populates the job name for you). Select the “Host at forge SVN” option, and in the drop-down window select the repository that was just created. Image images 5a and 5b, show this step.


Image 5: Create a new CloudBees Project and configure forge repositories 


Image 5a: New CloudBees Project


Image 5b: Configure “New CloudBees Project” information

Step 5: Point to the forge repository

Right-click on the forge repositories option, (on CloudBees window) as shown on image 6 and point your existing repository. Image 7 shows the configured repository.


Image 6: Configure forge repository


Image 7: Forge repository configured


Step 6: Inspect the default app

Inspect the default servlet app created and change it if desired. Image 8 shows the app in the IDE.


Image 8: Create a new servlet app

Step 7: Run the app in the local environment

Go to run and select “Run as” to run this application on the CloudBees local application development enviroment. This command fires up the internal “bees: run” command to deploy this to a local instance of Tomcat found on port 8335. Image 9 shows the command in the IDE and image 10 shows the default application.


Image 9: Run as (local or on RUN@cloud)


Image 10: App running locally (on port 8335)

Step 8: Deploy to RUN@cloud

If you're satisfied with the application running locally, then the next step is to deploy to the cloud. Go to run-“Run As” and deploy this application as a CloudBees application on RUN@cloud. This will take the application and deploy it on the RUN@cloud service on Image 11 shows the same app running on the PaaS.

Image 12 shows the updated status of this particular application as the IDE polls from from the RUN@cloud service.



Image 11 - Your application running on the PaaS


Image 12 - View of application running on the PaaS in Eclipse


The next steps are to build a continuous deployment environment by installing a CloudBees deployer plug-in on DEV@cloud. This is covered in a separate article.


We also have videos demonstrating the use of these plugins


Tags: eclipse
Created by Spike Washburn on 2011/07/08 00:48