Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Navigation:

Table of Contents


(blue star) 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.


  1. Ssh into the Mozart HySDS component of the provisioned cluster.

  2. Retrieve GitHub url of the repo containing the PGE code to be deployed.

...

  1. Image Added

  2. 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:

    Code Block
    sds ci add_job -b <BRANCH> <GITHUB_URL> s3

  3. Log into the Jenkins/CI interface and build project.

    1. Select the imported project from the project dashboard.

    2. Click the Build Now button in the left ribbon.

    3. Click the Console Output button in the left ribbon for the build output.

  4. 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.


Info

To remove/unregister PGE’s use the following:

Code Block
sds ci remove_job <GITHUB_URL>

(lightbulb) Have Questions? Ask a HySDS Developer:

Anyone can join our public Slack channelto learn more about HySDS. JPL employees can join #HySDS-Community

(blue star)

JPLers can also ask HySDS questions atStack Overflow Enterprise

(blue star)

Live Search
placeholderSearch HySDS Wiki