Morpheus Jenkins Task Plugin

By: Morpheus Data

As IT environments grow larger and more complex there’s a need to integrate disparate systems in order to deliver higher level IT outcomes. Morpheus recently released a new integration for the Jenkins CI server platform to help deliver end to end orchestration. The Jenkins Task plugin enables a new automation task type in Morpheus for triggering the build of Jenkins CI jobs. The task could be used to trigger Jenkins jobs for performing tasks such as deploying software onto provisioned infrastructure, validating the configuration of the system, and more.

In this blog post you’ll learn how to create a Jenkins automation task using the Jenkins plugin.

Downloading the Jenkins Plugin

The Jenkins Task Plugin is downloaded from the Morpheus Exchange where Morpheus curated plugins are hosted. Download the latest version of the plugin by clicking on the DOWNLOAD button to the right of the screen.

Morpheus Jenkins task plugin exchange page

Installing the Jenkins Plugin

With the plugin jar file downloaded to the local filesystem, you are now ready to install the Jenkins plugin on your Morpheus appliance. Install the plugin by uploading the plugin through the Morpheus UI from the Administration > Integrations > Plugins.

Generating a Jenkins Token

The automation task requires authentication credentials to enable Morpheus to trigger Jenkins build jobs. You need to generate an API token in Jenkins to enable Morpheus to trigger build jobs. The API token is associated with a Jenkins user or service account.

Creating a Jenkins Task

Once the plugin has been installed, there should be a new task type (Jenkins Trigger Build) that appears in the list of Morpheus automation task types. The task requires the API URL for the Jenkins server along with the authentication credentials, job name and any job parameters.

The example below triggers a job name examplejob and passes a parameter named name to the triggered job.

Morpheus Jenkins automation task configuration

Once the Morpheus automation task is executed, the Jenkins job should start. The screenshot displayed below is the Jenkins output from the triggered job. The job simply printed “Hello Martez” with “Martez” being the name parameter that was passed from the automation task.

Jenkins build status

This new integration simplifies the process of trigger CI jobs. The automation task could be added to provisioning workflows as part of server builds or exposed in a self-service fashion via operational workflows.

Join the Morpheus Community

Join the Morpheus community and engage other Morpheus community users to learn more about ways to use the platform. Also, downloading the Morpheus Community Edition lets you fully experience the Morpheus platform including nearly all features and capabilities! Register at Morpheus Hub and try it in your home lab or test environment today!

Related Resources

  • card listing image
    Jun 2024 | Blog
    Build vs. Buy? theCube looks at Hybrid Cloud Platform O...
  • card listing image
    May 2024 | Webinar
    Tech Brief: Integrating Morpheus and GitHub Actions
  • listing image
    May 2024 | Product
    Lab Guide: SuiteCRM Automation with Morpheus
  • listing image
    May 2024 | Solution
    Morpheus + Dell Solution Brief
  • listing image
    Apr 2024 | Solution
    Morpheus Orchestration for Edge Computing
  • card listing image
    Apr 2024 | Webinar
    Tech Brief: What’s New in Morpheus 7.0
  • listing image
    Mar 2024 | Blog
    NEWS: Hypervisor Independence from Broadcom and VMware
  • listing image
    Feb 2024 | Blog
    Reduce risk from the Broadcom acquisition with VMware a...
  • card listing image
    Nov 2023 | Video Demo
    The Morpheus Plugin Code Generator
  • listing image
    Oct 2023 | Paper
    Build vs Buy for Hybrid Cloud Platform Operations