Deploy PGE's onto Cluster
- Marjorie Lucas
- Topher Allen
Page Navigation: |
|---|
Confidence Level Moderate This article includes input from several JPLers. Multiple subject matter experts can indicate that a page is more frequently reviewed and updated. |
|---|
Introduction
Use this guide to import PGE’s from an existing codebase into Jenkins/CI then deploy them to Tosca/Figaro. This guide assumes a cluster has been provisioned.
Ssh into the Mozart HySDS component of the provisioned cluster.
Retrieve GitHub url of the repo containing the PGE code to be deployed.
Run the following command, where <BRANCH> is replaced with the branch to import and <GITHUB_URL> is replaced with the URL retrieved in step 2:
sds ci add_job -b <BRANCH> <GITHUB_URL> s3Log into the Jenkins/CI interface and build project.
Select the imported project from the project dashboard.
Click the Build Now button in the left ribbon.
Click the Console Output button in the left ribbon for the build output.
Verify the PGE was deployed to the Tosca HySDS component of the provisioned cluster by confirming the PGE shows up on the list of available actions when clicking on the Trigger Rule/On-Demand buttons.
To remove/unregister PGE’s use the following:
sds ci remove_job <GITHUB_URL>Have Questions? Ask a HySDS Developer: |
Anyone can join our public Slack channel to learn more about HySDS. JPL employees can join #HySDS-Community
|
JPLers can also ask HySDS questions at Stack Overflow Enterprise
|
Page Information: |
|---|
Was this page useful? |
Contribution History:
|
Subject Matter Expert: @Marjorie Lucas |
Find an Error? Is this document outdated or inaccurate? Please contact the assigned Page Maintainer: @Marjorie Lucas |