Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Creating a Jenkins 1.5 on RHEL 5.9 service offering

This topic describes the tasks that you must perform in BMC Cloud Lifecycle Management to create the service offering that the end user can then use to provision the application infrastructure (for example, an OS and an application package).

Note

Although services and service offerings are bundled with the zipkits, you might want to use the procedures to create a service and service offering to create or edit these artifacts.

It includes the following topics:

To create the service and the service offering

In the BMC Cloud Lifecycle Management Administrator console, you must add a service and a service offering.

For Jenkins 1.5 service blueprint, create a service and service offering based on the available deployment model. The Jenkins 1.5 Content-Pack supports the single-tier service deployment model. In the single-tier deployment model, Jenkins 1.5 is installed on a single instance of a server.

To create a service

Excerpt named creatingservice was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm45._CSMinclusionsLib._inclusionsLibZipKit._createServiceOfferings.WebHome.

To create a service offering

Excerpt named creatingserviceoffering was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm45._CSMinclusionsLib._inclusionsLibZipKit._createServiceOfferings.WebHome.

To make the provisioning request

  1. Access Workspaces > Service Instances to display the Service Instances workspace, and click New Service Request.
    serviceinstances_request1.png
  2. In the New Service Request dialog box, click the server provisioning service you want to display in the Submit Request dialog box.
    serviceinstances_request_submit.png
  3. Enter the data in the required fields to complete the request for an instance of the service request. You can click Next to review the details.
  4. Click Submit. The request is added to the Pending Activity list in the Service Instances window.

The request status is displayed in the Pending Activity list of the Service Instances window. You can double-click on the service request to see its detailed information.

For more detailed procedures, see Requesting-cloud-services and Requesting-cloud-services-in-the-legacy-console.

To validate the provisioned components

After provisioning the blueprint, you can validate the Jenkins 1.5 components setup in your environment.

Components

How to verify

Results

To access Jenkins home page

To access Jenkins homepage, visit the following URL:

http://<IP or Hostname or FQDNName>:8080

Note: kindly update URL as per your environment.

This displays Jenkins home page.

To verify Java

To verify Java, run the following command:

 

java -version

This displays Java version.

To verify Jenkins

To verify Jenkins, run the following command:

rpm -qa | grep -i jenkins

This command displays Jenkins version.

Where to go next

Once you have created the service offering, the cloud end user can request a service offering from the My Cloud Services Console. To view a list of tasks the cloud end user can perform to manage your cloud services, see Managing-cloud-resources in the BMC Cloud Lifecycle Management online technical documentation.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*